Licensing rehash

[HCHTech]

I'm looking at adding a couple of physical hosts to a site and just want to make sure I've got the licensing correct for User CALs.

Currently, there is a single physical host with 2 VMs, a DC and a production/application server. There are 18 users and we have 20 user CALs.

If I add a 2nd physical host to spin up a dedicated SQL server VM and add some additional file storage, I need another 20 user CALs since every user will be accessing the SQL server and shared storage (and SQL licenses as necessary, of course) correct?

If I add a 3rd physical host as a full-time backup target (We're looking at Quest Rapid Recovery - we use it with another client and have had a good experience) then I do NOT need user CALs for that host since no user will be accessing services on that host directly, correct?

Thanks for confirming - nobody likes going back to the client after they have approved your quote with additional charges.

 

[YeOldeStonecat]

USER CALs...you look at it as licensing the users. A single USER CAL allows a user to access any number of Windows Servers.
You need to license those additional servers of course...but you don't need to double up on your USER CALs.

20 USER CALs will allow up to 20 concurrent users to access a single server...or two servers...or three servers...or four servers, etc.
So you do not need another 20 USER CALS for shared storage of that 2nd or 3rd server.
BUT...yes you will need x amount of SQL client CALs. Checking with the software vendor first though...sometimes they include it in their package.

of course..check with your MS licensing desk at your wholesaler...cuz they can change often, but..that's how I've always approached it for abou 30 years.

 

[Sky-Knight]

Yes, User CALs only need purchased once per network, all users are authorized to access any number of servers with the matching service.

The only rub is ensuring that you have the right CALs for the right product. SQL can be licensed by the core, or by user CAL... and you'll want to take a close look because I think the per core licensing breaks even at 30 users. The rub here is you must license all the CPU cores on the server regardless of how many are used for the VM.

 

[mikeroq]

Yes, User CALs only need purchased once per network, all users are authorized to access any number of servers with the matching service.

The only rub is ensuring that you have the right CALs for the right product. SQL can be licensed by the core, or by user CAL... and you'll want to take a close look because I think the per core licensing breaks even at 30 users. The rub here is you must license all the CPU cores on the server regardless of how many are used for the VM.

You don't have to license all the physical cores if you are running in a VM. There is a 4 core minimum though.

Here is a calculator you can use to determine the costs and see if per core or SQL cal is cheaper:

MS SQL 2022 Std Licensing Calculator - WintelGuy.com

MS SQL Server Standard 2022 Licensing Calculator - estimates the number of required SQL Server licenses and related costs

wintelguy.com

Keep in mind that CALs offer backwards compatibility but not forwards.
For example if their current servers are Server 2016 and your new one is Server 2019 the existing CALs will not cover that. You will need to purchase new 2019 CALs to cover the users.

 

[HCHTech]

Thanks! - that's not the answer I was expecting - but good news nonetheless. Everything I read seemed to avoid saying those words "1 User CAL is good for multiple servers on the network" or similar. I appreciate the clarification.

 

[Sky-Knight]

You don't have to license all the physical cores if you are running in a VM. There is a 4 core minimum though.

Here is a calculator you can use to determine the costs and see if per core or SQL cal is cheaper:

MS SQL 2022 Std Licensing Calculator - WintelGuy.com

MS SQL Server Standard 2022 Licensing Calculator - estimates the number of required SQL Server licenses and related costs

wintelguy.com

Keep in mind that CALs offer backwards compatibility but not forwards.
For example if their current servers are Server 2016 and your new one is Server 2019 the existing CALs will not cover that. You will need to purchase new 2019 CALs to cover the users.

https://download.microsoft.com/download/e/2/9/e29a9331-965d-4faa-bd2e-7c1db7cd8348/SQL_Server_2019_Licensing_guide.pdf

I stand corrected... I got audited with SQL 2012 and would have had to pay the fine if not for re-licensing to SQL 2016 at the time. It seems with 2019 they changed it up again, and made it what I (and my rep) though it was in 2012.

So yes, physical or virtual, 2 2-core packs are the minimum.