Need some help with SQL Server 2016 Standard licensing (price confusion)
-
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
I did not realize that the license + CAL route allowed unlimited instances and/or cores. And we actually have a few other SQL Server 2008 R2 servers that need to be refreshed soon (a few are virtual and two are physical).
I could check with my Microsoft partner, who is actually also our Dell VAR... so I'm probably in need of finding a separate person who is solely a MS Partner and not a salesman.. unless I mean something other than partner.
A SQL Server License covers installation on a given physical server or guest.
This is a good place to start: http://mla.microsoft.com/
Run through Open with no SA to get a base cost for both options.
First time seeing the MLA. Really glad you gave me that link, thanks!
-
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
-
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
-
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
-
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
-
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
-
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
There is almost no reason for anyone in the normal, day to day, business world to use device CALs.
-
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
There is almost no reason for anyone in the normal, day to day, business world to use device CALs.
Agreed, this is super specific niche stuff normally reserved for manufacturing shift work.
-
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
If you need to even consider device CALs, you'll know. It's not something 90% of companies even need to think about.
And I bet you have a way different ration than you are imaginging. Every device like a printer requires a device CAL. Anything that uses DHCP... even IoT devices like light bulbs technically. So you count devices by "IPs used on the network" to get a rough starting point. It's crazy. Essentially no one can do it.
Count your users, use User CALs. Done.
-
@scottalanmiller said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
If you need to even consider device CALs, you'll know. It's not something 90% of companies even need to think about.
And I bet you have a way different ration than you are imaginging. Every device like a printer requires a device CAL. Anything that uses DHCP... even IoT devices like light bulbs technically. So you count devices by "IPs used on the network" to get a rough starting point. It's crazy. Essentially no one can do it.
Count your users, use User CALs. Done.
Ah, that clears up a lot of my confusion. I appreciate the valuable insight.
-
@scottalanmiller said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@jaredbusch said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@phlipelder said in Need some help with SQL Server 2016 Standard licensing (price confusion):
@dave247 said in Need some help with SQL Server 2016 Standard licensing (price confusion):
Hi friends.
I am working on building a new physical server to replace one which is running older versions of Windows and SQL server, plus it is almost out of storage space so this needs to be done sooner than later.
This SQL server is running a 3rd party application and they currently only support up to SQL 2016, so that's what I have to install - not 2017. And it's going to be SQL 2016 Standard Edition running on Windows 2016 Server Standard with 16 cores.
I spent a while researching SQL sever licensing to try and get an idea of how much it's going to cost. I haven't dealt with SQL server licensing yet.
First, I assumed that I would still have to purchase SQL Server 2017 core licenses with downgrade rights. So looking on the SQL Sever Pricing page, it looks as though Standard - per core price is $3,717 (2 pack). So if my server has a total of 16 cores, this is going to cost about $29,736 to cover SQL licensing.
Then I checked over on CDW just to get an idea of prices and things and I had the idea to search "SQL 2016" when I found this: SQL Server 2016 Standard - license - 16 cores - with Server 2016 Standard for like $1,900.
Is this even applicable to what I'm doing or am I missing something? It does say in the technical details "BIOS locked (Lenovo)" but I have no idea what that refers to. But other than that, it looks like it's licensing SQL Server 2016 for 16 cores and bundled with Windows Server 2016. Surly this can't be correct... or is it? If it is actually what I would need to be covered, I would purchase it, of course.
Otherwise, can someone help me get an idea of what I should be paying for SQL Server 2016 Standard Edition for 16 cores if not the cost I initially calculated ($29,736)? And I don't think we'd do the server + cal licensing as we have about 80 users and 100 or more systems which would connect to the SQL server.
Simple rule of thumb to ask your Microsoft licensing rep for the following:
First option is license + CALs that allows internal access only with unlimited instances on the server and unlimited cores:- SQL Server Standard License
- SQL Server Standard User CALs (80 Users)
Second option is per core with a minimum of 4 to purchase:
- SQL Server Standard Per Core 2-Pack (2x)
In the Per Core scenario we can license for the number of physical cores to use and delimit that in SQL Studio Management. When it comes to audit, a snip of that setting that only allows the four threads should be just fine.
So if you license + CAL, do you have to cover all users AND computers?
If you license by user you cover users. If you license by device you cover devices.
Well what constitutes as a device? I mean, users use a device to connect to the SQL server... so wouldn't I have to cover both? I don't get it.
That is never how Microsoft CALs have worked.
ok, I finally re-read the overview.. makes sense again. We have a pretty even user/device ratio with slight fluctuations in both over time. I suppose we'd just do user CALs..
There is almost no reason for anyone in the normal, day to day, business world to use device CALs.
Agreed, this is super specific niche stuff normally reserved for manufacturing shift work.
We have a few clients that run two or three shifts across one or more facilities. A shared device by two or three peeps per day is about the only time we've ever deployed Device CALs.
