I read the multiple articles for SQL, still not clear.
I have a HP server with 2 six core E5-2650 2.5Ghz processors.
So I have;
And 60 concurrent client workstations accessing this database server.
And I have to purchase licenses for SQL 2014 which will be installed as a VM in the HP box.
1. If I configure 4 virtual processors for the new SQL VM in Hyper-V manager, how many core licenses do I have to purchase? (When I configure 4 virtual processors, in Task Manager of the VM, it shows 4 cores, so I assume Hyper threading is not involved in the licensing).
2. What is the cheaper way, core or cal?
Current market price for SQL 2014 STD;
sql 2014 server $900
sql 2014 server core $3600 (2 cores)
sql 2014 device cal $200
To serve 60 concurrent client accesses, I guess 3-4 virtual processor assignments seem reasonable power it needs, so if I go with core licensing model, which pricing is correct?
a. Needs 4 core SQL licenses: 2 X $3600 = $7200
b. 12 core SQL licenses: 6 X $3600= $21600
3. When License violation happens..
Let's say I purchased 2 core SQL licenses, but then later I found, it's not sufficient, so I increased the number of vcores from 2 to 4 in Hyper-v Manager. If then, what happens, will that make my SQL go down or give grace period or there's no any enforcement of licensing to operation?
4. Licensing for live migrartion.
And also I have to figure how Hyper-v live migration or clustering will affect SQL licensing. If I move the SQL server to a different Hyper-v host, does it require any additional license?
What happens when I move the SQL server to a server which has more cores but the number of vcore of the SQL VM remains the same? If licensing follows only number of vcore, I guess it doesn't matter, does it?