What are the key benefits of Microsoft SQL 2017 User CAL?
User licensing – License one person across multiple devices.
Cost control – Pay only for users who access SQL.
Compliance clarity – Straightforward way to stay properly licensed.
Access flexibility – Supports local, remote, and app based access.
Growth friendly – Add users anytime without relicensing server.
Small business – Ideal for limited user database environments.
This product allows a one-time activation for one device. Once used, it cannot be used again, not even for the same device.
A key can activate the software once.
Access right – Legal permission for one user to reach SQL Server.
Cross-device use – One person connects from laptop, desktop, phone.
Edition coverage – Grants access to SQL Server 2017 Standard.
Indirect access – Covers connections made through apps or middleware.
Version scope – Also reaches SQL Server 2016 and older instances.
Important – No server software, server license, or activation key is included here.
Core Capacity – Licenses one named user, unlimited devices for that person.
A SQL Server 2017 User CAL is the access license that legally entitles one named person to use a SQL Server 2017 Standard instance under the Server plus CAL model. It is paired with a SQL Server license and does not contain the database software itself.
Person-based – Follows the user across every device they use.
Mobile workers – Fits staff switching between office and home machines.
Predictable cost – Cheaper than core licensing for small, countable teams.
No reinstall – Paper license adds users without touching the server.
Audit safety –Documents legal access for Microsoft compliance checks.
Backward reach – The 2017 CAL also covers older SQL versions.
A User CAL grants one specific person the right to access a SQL Server 2017 instance, regardless of how many devices that person uses to connect. It is required under the Server plus CAL licensing model, where each accessing user or device must hold its own CAL. The CAL itself is a legal entitlement, not installable software, so there is no key to activate and nothing to deploy on a workstation. It must always sit alongside an actual SQL Server 2017 Standard license, which provides the database engine. Buying a CAL on its own gives access rights but no working server.
A User CAL is tied to one named person, who can then connect from any number of devices, while a Device CAL is tied to one machine that any number of people can share. Choose User CALs when employees use several devices each, such as a laptop, a phone, and a remote home PC, because one User CAL covers all of them. Choose Device CALs for shared endpoints like shift PCs, warehouse terminals, or kiosk stations used by many staff in turn. For most modern offices where each worker has multiple devices, User CALs cost less than buying a Device CAL for every endpoint that person touches. The two types cannot be mixed on the same access path to reduce the count below what each rule requires.
| Aspect | User CAL | Device CAL |
|---|---|---|
| Licensed to | One person | One device |
| Multiple devices per user | ✓ | ✕ |
| Multiple users per device | ✕ | ✓ |
| Best for | Mobile staff | Shared terminals |
| Needs server license | ✓ | ✓ |
It suits small and mid-sized organizations running SQL Server 2017 Standard under the Server plus CAL model with a clearly countable number of users. The User CAL specifically fits teams where individuals each use several devices, since one CAL follows the person rather than the hardware. It solves a concrete problem that core licensing does not address well at small scale: when only a handful of named staff need database access, paying per user is usually cheaper than licensing every CPU core. It is the wrong fit for public web applications or extranets, where user numbers fluctuate and cannot be counted cleanly; those scenarios point toward Per Core licensing instead.
No. A User CAL is only an access license and contains no database software and no server license. You must already own a SQL Server 2017 license for the engine; the CAL is then added on top to make each user's access legal. The server license alone covers up to two users or devices, but strictly for administering the instance, not for normal day-to-day use. Because the CAL is a paper entitlement, it has no installer and no activation key, unlike RDS CALs. If you only buy CALs without a server license, you have access rights to a server that does not yet exist in your environment.
No, CALs are not forward compatible: a 2017 User CAL cannot legally cover access to SQL Server 2019, 2022, or 2025. It works the other way around — a 2017 CAL can access SQL Server 2017, 2016, and earlier instances, because newer CALs are backward compatible. The practical rule is that the CAL version must match or exceed the highest server version it touches. This matters during upgrades: if you move the database engine to SQL Server 2019, your existing 2017 CALs no longer keep that access compliant and must be upgraded. Plan CAL versions around the newest SQL Server you intend to run, not the oldest.
Yes. Under Microsoft's multiplexing rule, pooling or routing connections through a middle tier, web front-end, or service account does not reduce the number of CALs required. Each user or device that ultimately benefits from the SQL data still counts as an accessing user and needs its own CAL. This is one of the most common compliance gaps found in audits, because teams assume a single service-account connection means a single license. The rule applies whether SQL Server runs physically, virtually, or in a container. When access cannot be cleanly counted because of heavy multiplexing or external users, Per Core licensing is often the safer model.
First confirm you are licensing under the Server plus CAL model and not Per Core, because the two do not mix and Per Core needs no CALs at all. Count your named users honestly, including external contractors, since each needs a separate User CAL regardless of how many devices they use. Verify the SQL Server edition is Standard, as Server plus CAL is no longer sold for new Enterprise deployments. Check the version match so the CAL is the same as or newer than the server it will access. As a rough threshold, once you exceed roughly fifty users or have unpredictable access, Per Core licensing usually becomes the more economical and lower-risk choice.
| Important | To use Microsoft SQL 2017 User CAL, your server must meet the Microsoft SQL Server 2017 Standard host requirements and SQL Server licensing compatibility hardware and software specifications. |
| Compatibility | Microsoft SQL Server 2017 Microsoft SQL Server 2016 Microsoft SQL Server 2014 Microsoft SQL Server 2012 Microsoft SQL Server 2008 R2 Microsoft SQL Server 2008 |
| Operating Systems | Windows 11 and 10: Home / Pro / Enterprise / IoT Enterprise Windows 8.1: Pro / Enterprise Windows 8: Core / Pro / Enterprise Windows Server 2022: Standard / Datacenter / Datacenter Azure Edition Windows Server 2019 and 2016: Essentials / Standard / Datacenter Windows Server 2012 R2 and 2012: Foundation / Essentials / Standard / Datacenter Red Hat Enterprise Linux 8.x Server Red Hat Enterprise Linux 7.7 to 7.9 Server SUSE Linux Enterprise Server 12 SP3 to SP5 Ubuntu 18.04 LTS Docker Engine 1.8 or newer on Linux |
| Processor | x64 processor. All Intel and AMD x86-64 CPUs with up to 64 cores per NUMA node. Minimum speed 1.4 GHz. Recommended speed 2.0 GHz or faster. |
| Memory RAM | Minimum 1 GB. Recommended at least 4 GB. Memory should be increased as database size increases to ensure optimal performance. |
| Hard Disk | Minimum 6 GB available hard drive space. Drive space requirements vary with the SQL Server components you install. |
| Display | Super VGA 800x600 or higher-resolution monitor. |
| Graphics | Integrated or dedicated graphics capable of Super VGA 1024 x 768 or higher resolution. |
| Note | A User CAL is a licensing entitlement and has no device-side hardware requirements. Actual requirements depend on the Windows Server version used to host SQL Server 2017, selected SQL Server features, and workload size and concurrency. Requires .NET Framework 4.6 for Database Engine, Master Data Services, or Replication. Internet functionality requires Internet access. The minimum memory required for installing the Data Quality Server component in Data Quality Services is 2 GB of RAM. |
keys.express and keys.discount are online platforms for product keys. The product keys available in our shops for Windows and other software are inexpensive, secure, legal and come with an activation guarantee.
Below you will find the most important legal information about our products.
We offer exclusively unused and non-activated product keys. The keys have never been redeemed for activation and are fully available to the purchaser for the first-time activation of the respective product. A key that has already been redeemed could no longer be used for a new activation and is therefore not offered by us.
Trading in these product keys is permissible in the European Union and in Switzerland under current case law, provided that the necessary conditions are met. These conditions are as follows:
This trade is legally permissible because the underlying license was already placed on the market with the consent of the rightholder within the EU/EEA or Switzerland in return for appropriate remuneration. As a result, the so-called principle of exhaustion has taken effect, which permits the resale of individual product keys — in particular those originating from volume license agreements. Microsoft or the respective software provider has already received appropriate remuneration for this.
keys.express and keys.discount ensure that the aforementioned conditions are met and that the lawful use of the software is guaranteed. The requirements arising from European legislation are also observed in Switzerland.
Important note: The acquisition of a product key through the transmission of a combination of numbers and letters in digital form does not, in itself, constitute a license for the lawful use of the program. The license only arises from the respective installation and the associated acceptance of the manufacturer's terms of use.
Further information can be found here: