What is included in Microsoft SQL 2025 Device CAL?

Device access right – Licenses one device to reach SQL Server.
Unlimited users – Any number of people share that licensed device.
Standard edition use – Valid in the Server plus CAL model.
Indirect access covered – Includes middleware, ERP, and reporting access.
Backward compatible – Reaches SQL Server 2019 and 2017 servers.
Core Capacity – No server software included; license the SQL instance separately.

What are the main benefits of Microsoft SQL 2025 Device CAL?

A Device CAL is a Client Access License that authorises a single device to connect to a SQL Server 2025 Standard instance licensed under the Server plus CAL model. It covers every user who works from that one machine, so it suits shared terminals rather than per-person licensing.

Shared device value – One license covers shift workers on a terminal.
Predictable cost – Count devices instead of fluctuating staff numbers.
Multiplexing safe – Covers indirect access through pooling or apps.
Mixed licensing – Combine with User CALs on the same server.
Version flexibility – One CAL connects to older SQL servers too.
Audit clarity – Device-based counting is easy to document.

SQL Server 2017–2025 Buying Guide: License Models and CALs
How Per Core and Server plus CAL work, and how to choose between User CAL and Device CAL without overpaying.

What does a SQL Server 2025 Device CAL actually do?

A Device CAL gives one physical device the right to access a SQL Server 2025 Standard instance, no matter how many people use that device. It is an access license only, so it does not install or run SQL Server itself; you still need the server software licensed under the Server plus CAL model. This is why a CAL is bought in addition to the SQL Server license, not instead of it. In practice, a single front-desk PC or warehouse terminal used by a whole shift needs only one Device CAL rather than one license per worker.

Who is the SQL Server 2025 Device CAL best suited for?

Device CALs fit organisations where many people share a small number of fixed machines, such as call centres, point-of-sale tills, production line terminals, or nurse stations. The licensed unit is the device, so a kiosk used by three rotating shifts still counts as one CAL instead of the dozens of users passing through it. This solves the specific problem of high user turnover on shared hardware, where User CALs would force you to license every individual even though they never connect from their own device. If staff instead roam between laptops, phones, and remote sessions, a User CAL is usually the cheaper and cleaner fit.

What is the difference between a User CAL and a Device CAL for SQL Server 2025?

A User CAL licenses a named person to access SQL Server from any number of devices, while a Device CAL licenses one machine for use by any number of people. The right choice depends purely on the ratio: fewer devices than users favours Device CALs, fewer users than devices favours User CALs. Both types attach to SQL Server 2025 Standard under the Server plus CAL model and cannot be used with the Enterprise edition, which is core-licensed only. You can mix both CAL types against the same server, which is common when office staff get User CALs and shared shop-floor terminals get Device CALs.

SQL Server 2017–2025: Core Licensing and Avoiding Incorrect Purchases
When Per Core beats Server plus CAL, and the mistakes that lead to missing or wasted access licenses.

Does the SQL Server 2025 Device CAL cover indirect access through other applications?

Yes. Under Microsoft's multiplexing rule, any device that reaches SQL Server data through middleware, an ERP front-end, a web application, or connection pooling still needs a CAL, even when a single service account handles the actual connection. The licensing is based on who or what ultimately uses the data, not on the number of technical connections. This catches many buyers out: routing everyone through one application login does not reduce the CAL count. For Device CALs specifically, you count the distinct devices that benefit from the data, regardless of how the connection is bundled.

What should you check before choosing the SQL Server 2025 Device CAL?

First confirm your SQL Server 2025 instance is Standard edition and licensed under Server plus CAL, because Device CALs do not apply to the Enterprise edition, which is sold per core only. Then count the fixed devices that connect, including indirect access points, since the device is the billable unit. A Device CAL only makes financial sense when devices clearly outnumber users; if individuals connect from several machines, a User CAL avoids buying multiple CALs for the same person. Also keep in mind that the CAL is an access license, so the SQL Server software still needs its own server license.

SQL Server 2017–2025 FAQ: Standard, Enterprise, and CALs
Common questions on edition differences and when CALs are required, answered for buyers.

Frequently asked questions about Microsoft SQL 2025 Device CAL

Is a SQL Server 2025 Device CAL backward compatible with older servers?

Yes. A SQL Server 2025 CAL can be used to access earlier server versions such as SQL Server 2019 or 2017. This lets you standardise on the latest CAL while still connecting to mixed-version environments during a phased upgrade.

Does a Device CAL include the SQL Server software?

No. A Device CAL only grants access rights for one device; it does not include or activate the SQL Server engine. You must separately license the SQL Server 2025 Standard instance under the Server plus CAL model for the CAL to have anything to connect to.

Can Device CALs and User CALs be used together on the same SQL Server?

Yes. The two CAL types can be mixed against the same Server plus CAL instance. A common setup assigns User CALs to mobile staff and Device CALs to shared terminals, which keeps the total count lower than using one type for everyone.