April 4, 2015 at 7:35 am
It is my understanding that SQL Server 2014 is Licensing by core with a minimum of 4 cores per CPU.
What impact does having multiple instances have on pricing if any?
Any input would be greatly appreciated. 🙂
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
April 7, 2015 at 3:32 pm
it appears that if you buy four core licenses for a server you could put multiple SQL server instances on that server. this is from the SQL Server 2014 Licensing Guide (emphasis is from the doc)
Under the Per Core licensing model, each server running SQL Server
2014 software or any of its components (such as Reporting Services or
Integration Services) must be assigned an appropriate number of SQL
Server 2014 core licenses. The number of core licenses needed depends
on whether customers are licensing the physical server or individual
virtual operating system environments (OSEs).
April 7, 2015 at 4:07 pm
Robert klimes (4/7/2015)
it appears that if you buy four core licenses for a server you could put multiple SQL server instances on that server. this is from the SQL Server 2014 Licensing Guide (emphasis is from the doc)Under the Per Core licensing model, each server running SQL Server
2014 software or any of its components (such as Reporting Services or
Integration Services) must be assigned an appropriate number of SQL
Server 2014 core licenses. The number of core licenses needed depends
on whether customers are licensing the physical server or individual
virtual operating system environments (OSEs).
What if it is virtual as opposed to physical?
What is the difference?
Thanks.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
April 7, 2015 at 4:10 pm
As far as I know it's based on the number of physical cores running some form of SQL Server component regardless of how many or which mix of components or virtual machines etc...
April 7, 2015 at 4:29 pm
Welsh Corgi (4/7/2015)
What if it is virtual as opposed to physical?
What is the difference?
Thanks.
If you are buying SQL Standard core-based licenses then I'm pretty sure it doesn't matter whether is is virtual or physical.
April 7, 2015 at 4:37 pm
Robert klimes (4/7/2015)
Welsh Corgi (4/7/2015)
What if it is virtual as opposed to physical?
What is the difference?
Thanks.
If you are buying SQL Standard core-based licenses then I'm pretty sure it doesn't matter whether is is virtual or physical.
Thanks. I will be buying mostly Stabrd but some Enterprise Licenses.
What hapens for the Enterprise Editions?
Thanks.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
April 7, 2015 at 6:03 pm
with enterprise you have some options with virtualization . You can still buy per-core for each server but if you purchase a core license for all physical cores then you can have as many VMs with a sql instance.
ie if you have a dual quad core server(8 cores) and you buy 8 core licenses, you would be able to have Eight 8-core VMs, all with enterprise. If you also have software assurance, you would be able to have unlimited VMs.
a bonus to this model is that if you have hyperthreading enabled, you would be able to create 8 (or unlimited with SA) 16 core VMs because you only have to license the physical cores but 16 cores would be available to your VMs.
a downside of this model is mobility of VMs. If you have four servers in your VM infrastructure and you wanted to be able to migrate your SQL server VMs to all four of the servers then you would have to fully license all physical cores. You could just license two or three physical servers and just put in rules to only allow your VMs to migrate to those hosts.
April 8, 2015 at 7:50 am
I just wanted to add something about the multi-instance setup. I think it is only valid for multiple instances of the same version. If you had a 2014 and a 2012 instance you would have to license both. This may also apply to different SP/CU builds, not sure though.
April 11, 2015 at 4:46 am
You totally need to talk to your Microsoft License Reseller.
You need to tell them what you plan to do, including if the server will be running real or virtual, your own DC, a CoLo or in the cloud, the SQL edition, the number of instances, and maybe other information.
The Microsoft License Advisor (mla.microsoft.com) can give you a 'raw' price, but the actual price you pay depends on the details of your licensing, which only your reseller will be able to tell you about.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply