Microsoft SQL 2017 User CAL Key (1)

A SQL Server 2017 User CAL is the client access licence one named person needs to use SQL Server licensed under the Server + CAL model. This listing is 1 User CAL, which covers that person on any number of devices. It isn't a server licence and doesn't include SQL Server itself. You get the licence key by email after payment, together with instructions.

• 1 User CAL for SQL Server 2017
• Covers one named user on any number of devices (PC, laptop, tablet, phone)
• Needed only for servers licensed under Server + CAL, not per core
• Also covers access to earlier SQL Server versions
• Digital delivery: nothing is shipped

When is a SQL Server User CAL the right choice?

Choose User CALs when each person uses more than one device to reach the database, for example an office PC, a laptop and a phone. One User CAL covers all of that person's devices, so you buy one CAL per person instead of one per device.

How many SQL Server 2017 CALs do I need?

You need one User CAL for every person who accesses SQL Server, directly or indirectly. That includes people who never open SQL Server tools but use an app, website or report that reads from the database.

Microsoft's licensing terms say that multiplexing, such as pooling connections through an application, web server or middleware, doesn't reduce the number of CALs required. Access from another licensed server doesn't need a CAL.

If you can't count your users, for example with a public website, core-based licensing is usually the better model because it needs no CALs at all. Compare the options in SQL Server 2017 licences.

What do I need before buying SQL Server 2017 CALs?

You need a SQL Server server licence that uses the Server + CAL model. CALs only grant access: they don't include SQL Server, and they don't replace a server licence.

How do I use and record SQL Server CALs?

In most cases there's nothing to type into SQL Server: CALs have no activation step, and SQL Server doesn't count connections for you. They are licences you keep on record and can show if your licensing is ever reviewed.

1. Check that the server runs SQL Server Standard licensed under the Server + CAL model.
2. List every person who reaches the database, including through business apps and reports.
3. Buy one CAL for each entry on that list, choosing User or Device CALs (or a mix).
4. Keep your order email and licence key with your licence records as proof of purchase.
5. Recount when staff or devices change, and add CALs before access grows.

A common mistake we see is buying CALs for a server that is licensed per core: those CALs aren't needed. The opposite mistake is counting only database administrators and forgetting the staff who reach the data through business apps.

Frequently asked questions

Does a SQL Server 2017 CAL work with older SQL Server versions?

Yes. Microsoft's licensing terms let a CAL access the corresponding version of SQL Server or earlier versions. A SQL Server 2017 CAL therefore covers SQL Server 2017 and older servers, but not a newer version released later.

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

No. They are separate licences. A SQL Server CAL covers access to SQL Server, while a Windows Server CAL covers access to the Windows Server operating system. A user of a SQL Server running on CAL-licensed Windows Server usually needs both.

Can I mix User and Device CALs?

Yes. You can use User CALs for staff with several devices and Device CALs for shared PCs on the same server. What matters is that every user or device accessing SQL Server is covered by one of the two.

How long will SQL Server 2017 be supported?

Mainstream support for SQL Server 2017 ended in October 2022, and extended support continues until October 2027. After that date Microsoft stops releasing security updates for it. Microsoft lists the exact dates on its SQL Server 2017 lifecycle page.

See all SQL Server 2017 licences and CALs, or browse Windows Server licences for the server itself.