tom_szabo
asked on
Is this the correct amount of licenses for Server 2016 and SQL 2017?
Ok so I want to be sure that this is correct.
So the setup is going to be a Windows 2016 Standard VM assigned with 4 Cores running SQL 2017 Standard
So if I buy a Server 2016 Standard ($882) then purchase 30 CALS for it, then buy 2x SQL 2017 Standard 2 Core packs (so 4 Cores total licensed)
Then I can have 30 users access the SQL server and be in compliance with Microsoft licensing?
So the setup is going to be a Windows 2016 Standard VM assigned with 4 Cores running SQL 2017 Standard
So if I buy a Server 2016 Standard ($882) then purchase 30 CALS for it, then buy 2x SQL 2017 Standard 2 Core packs (so 4 Cores total licensed)
Then I can have 30 users access the SQL server and be in compliance with Microsoft licensing?
You don't need to buy CALs AND core licenses. SQL Server is licensed either by CAL or by core.
ASKER
You don't need to buy CALs AND core licenses. SQL Server is licensed either by CAL or by core.
The CALS are for Server 2016, as I understand, you require a CAL for every user connecting to the server, then you need will need an aditional SQL CAL for each user connecting to the SQL database on that same Server. But in this case it was cheaper to go for core based licensing on SQL rather than SQL CALS.
Or do I have this completely wrong?
Tom,
Actually, I think you've got it right. You have to worry about two licenses here. One for Windows Server and one for SQL Server.
On the Windows Server side, you need a license for the Server OS itself, and you need CALs for the users or devices. Keep in mind that you can also look into Windows Server 2016 Essentials if you have less than 50 users accessing the server. You're limited to a single OSE (Operating System Environment), so you can either have a VM or run the physical server itself as the SQL server.
For the SQL Server, you're right about that, too. You can either purchase the server license and CALs or you can purchase the cores. The core licenses are sold in 2-packs and you have to cover all of your cores.
Licensing guide for Windows Server - https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing.
Licensing guide for SQL Server - https://www.microsoft.com/en-us/sql-server/sql-server-2017-pricing.
Let me know what you think.
Actually, I think you've got it right. You have to worry about two licenses here. One for Windows Server and one for SQL Server.
On the Windows Server side, you need a license for the Server OS itself, and you need CALs for the users or devices. Keep in mind that you can also look into Windows Server 2016 Essentials if you have less than 50 users accessing the server. You're limited to a single OSE (Operating System Environment), so you can either have a VM or run the physical server itself as the SQL server.
For the SQL Server, you're right about that, too. You can either purchase the server license and CALs or you can purchase the cores. The core licenses are sold in 2-packs and you have to cover all of your cores.
Licensing guide for Windows Server - https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing.
Licensing guide for SQL Server - https://www.microsoft.com/en-us/sql-server/sql-server-2017-pricing.
Let me know what you think.
What you've not stated is HOW MANY CORES in the Physical Host, because all CORES in the HOST must be licensed!
So how many cores and processors in the HOST server ?
So how many cores and processors in the HOST server ?
Important question: What is the use-case scenario for this server?
If it is only for hosting SQL Server, then you either need SQL Server CAL's or SQL Server Core licenses. And imho you need only to license virtual cores. Not physical one.
If it is only for hosting SQL Server, then you either need SQL Server CAL's or SQL Server Core licenses. And imho you need only to license virtual cores. Not physical one.
ASKER
Well this thread really goes to show how vauge and misleading Microsoft licensing rules are, everyone seems to have interpretted the rules differently...
It's not that bad, LOL. There are just multiple scenarios.
The links I sent are correct. The question is, how are you using your server?
The links I sent are correct. The question is, how are you using your server?
@Tom,
you've still not answered....
What you've not stated is HOW MANY CORES in the Physical Host, because all CORES in the HOST must be licensed!
So how many cores and processors in the HOST server ?
you've still not answered....
What you've not stated is HOW MANY CORES in the Physical Host, because all CORES in the HOST must be licensed!
So how many cores and processors in the HOST server ?
@Andrew: Sure? Cause this is the actual cheat sheet; and also what our local dealer says:
SQL Server 2017 Licensing Datasheet
SQL Server 2017 Licensing Datasheet
So the setup is going to be a Windows 2016 Standard VM assigned with 4 Cores running SQL 2017 Standard
It states Windows 2016 VM..... so it's a virtual machine on a Host... what is the host and and how many cores and processors ?
Licenses required are Windows OS and SQL ?
I'm referring to Windows OS licenses ? from what I've read above nobody seems to have mentioned ALL Cores in Host MUST be licensed for Windows 2016
*All physical cores on the server must be licensed, subject to a minimum of 8 core licenses per physical processor and a minimum of 16 core licenses per server.
Source
https://www.microsoft.com/en-us/licensing/product-licensing/windows-server-2016.aspx
ASKER
Ok so we got another quote for the licenses and we have decided to go with CALS for both Server and SQL.
So:
2016 Server Standard + 30 CALS
2017 SQL Standard + 30 CALS
This should take the "Cores" out of the equation I assume?
The physical host has 16 real cores, but we will still only assign proboubly 4 or 8 cores to this VM.
So:
2016 Server Standard + 30 CALS
2017 SQL Standard + 30 CALS
This should take the "Cores" out of the equation I assume?
The physical host has 16 real cores, but we will still only assign proboubly 4 or 8 cores to this VM.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So the quote is as follows
1x MW 228-11135 SQL Server 2017 - STANDARD Ed License (Requires CALs)
35x MW 359-06557 SQL Server 2017 - CAL - USER
1x MW 9EM-00118 Windows Server STANDARD Ed 2016 (Core Lic)OLP 16L NO LEVEL CORE
35x MW R18-05123 Windows Server CAL 2016 (OLP) USER CAL
The server license 9EM-00118 seems to cover 16 cores, so should be all good then?
1x MW 228-11135 SQL Server 2017 - STANDARD Ed License (Requires CALs)
35x MW 359-06557 SQL Server 2017 - CAL - USER
1x MW 9EM-00118 Windows Server STANDARD Ed 2016 (Core Lic)OLP 16L NO LEVEL CORE
35x MW R18-05123 Windows Server CAL 2016 (OLP) USER CAL
The server license 9EM-00118 seems to cover 16 cores, so should be all good then?
Yes, that looks correct.
If you have a single processor with 16 Cores, then the following is needed...
1 x Base License Required - Windows Server® 2016 Standard (16 core)
Which is correct, which entitles you to run up to a maximum of 2 VMs.
1 x Base License Required - Windows Server® 2016 Standard (16 core)
Which is correct, which entitles you to run up to a maximum of 2 VMs.
ASKER
Thanks
Standard
Limited to lesser of 4 sockets or 24 cores
from the MS page - Editions and supported features of SQL Server 2017
it looks like you only need to purchase one SQL Server license instead of two.