What is included in Microsoft SQL 2017 Device CAL?

Device access right – Licenses one device to reach SQL Server 2017.
Shared device cover – Any number of users on that device.
Network-wide reach – The device may access multiple licensed SQL Servers.
Edition independence – One CAL type, no separate Standard/Enterprise CAL.
Indirect access counted – Middleware and pooled connections still need this CAL.
Important – SQL Server software, the server license, and Windows CALs are not included.
Core Capacity – A 2017 CAL covers 2017 and earlier servers only.

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

A SQL Server 2017 Device CAL is a Client Access License that authorises one physical device to access SQL Server in the Server plus CAL model. It is a licensing right, not installable software, and is only needed when the server is not licensed per core.

Per-device pricing – Cheaper when many people share few machines.
Shift-work friendly – One CAL covers all users on a terminal.
Multi-server use – One device reaches every SQL Server on the network.
Downgrade coverage – Also licenses access to 2016, 2014, 2012 servers.
Audit clarity – Fixed device count is easy to document.
No core counting – Avoids per-core licensing on small deployments.

What does the SQL Server 2017 Device CAL actually do?

It grants one named device the legal right to access a SQL Server 2017 instance licensed under the Server plus CAL model. The CAL is not a software component and nothing is installed on the server; you assign it to a device and keep proof for compliance. Any number of users working from that single device are covered, which is why it suits shared shop-floor PCs, point-of-sale terminals, or kiosks. Each device CAL also reaches multiple licensed SQL Servers across the same network, not just one machine.

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

A Device CAL licenses one device for unlimited users, while a User CAL licenses one person across unlimited devices. Device CALs are the cheaper choice when several staff share the same workstation, such as in shift rotations, warehouses, or production lines. User CALs win when individuals use many devices, work remotely, or carry laptops and phones. The two types cannot be mixed on the same access right, but an organisation can buy both and apply each where it fits.

SQL Server 2017-2025 Buying Guide: License Models and CALs
How Server plus CAL and Per Core differ, when User or Device CALs make sense, and how to avoid the wrong model.

Does the SQL Server 2017 Device CAL include the SQL Server software?

No. A CAL is purely an access right and contains no software, no installer, and no server license. You still need a separate SQL Server 2017 server license assigned to the machine running the database, plus one CAL for every device that accesses it. The two CALs bundled with a server license are intended for administration only, not for regular users. SQL Server CALs are also separate from Windows Server CALs, so accessing the underlying Windows host may require its own licensing.

Can a 2017 Device CAL access newer SQL Server versions?

No. A CAL must always be the same version as the server or newer, so a 2017 CAL is valid for SQL Server 2017 and earlier releases such as 2016, 2014, and 2012, but not for 2019, 2022, or 2025. This backward-only rule means a newer 2022 CAL can reach a 2017 server, but never the reverse. If you plan to upgrade the database engine soon, buy CALs matching the highest server version you expect to run. Without Software Assurance, older CALs cannot be carried forward to a newer server.

SQL Server 2017-2025: Core Licensing and Avoiding Wrong Purchases
When per-core licensing beats Server plus CAL, minimum core requirements, and the buying mistakes that lead to non-compliance.

What should you check before choosing a Device CAL?

Confirm three things: the server runs Standard edition under the Server plus CAL model, the number of accessing devices is countable, and indirect access is accounted for. Enterprise edition has been per-core only since SQL Server 2012, so CALs do not apply there. Multiplexing rules mean that pooling connections through middleware or an ERP layer does not reduce how many CALs you need, because the end devices still count as accessing. Server plus CAL is also not permitted where users cannot be counted, such as public web applications, where per-core licensing is required instead.

Frequently asked questions about Microsoft SQL 2017 Device CAL

Do I need a CAL if my SQL Server is licensed per core?

No. Per-core licensing covers unlimited users and devices, so no User or Device CALs are required. CALs apply only to the Server plus CAL model used with Standard edition.

Can one Device CAL access several SQL Servers?

Yes. A single Device CAL lets that device access any number of licensed SQL Servers on the same network. The version rule still applies, so each server must be 2017 or older.

Is the SQL Server CAL the same as a Windows Server CAL?

No. SQL Server CALs are product-specific and do not grant access to Windows Server. If users also access the underlying Windows host directly, separate Windows Server CALs are needed.

SQL Server 2017-2025 FAQ: Standard, Enterprise and CALs
Answers to common buyer questions on edition differences, CAL requirements, and choosing between Standard and Enterprise.