The pricing model is a little confusing as it is per core, but will be on a esxi vmware host - but i assume it will be looked at for the number of cores i assign it within vSphere.
Please assist in understanding the true cost (server license or server license plus CAL?) of creating a new VM with that version, one SQL instance with multiple databases.
This document explains it in more details: https://www.itprotoday.com/business-resources/overview-sql-server-2016-licensing
Talk to a knowledgeable vendor. SQL Server pricing is too complex now to try to wing it on your own, even with Google's "help".
2. Express edition is free for production, but if has limited functionality. It is good to start production use and complete initial load. Later you can upgrade it to Standard.
3. On the moment license real cores or virtual cores is almost the same.
4. Licensing virtual cores is good if you need less cores than your host has.
5. Licensing physical cores allows you to run several VMs on the same host.
6. To be able to move VM to another host you need SA. SA allows you version upgrade as well (like from SQL Server 2012 to SQL Server 2014).
For production it is better "Per core" - unlimited users/devices.
For test/development use (1).
1. One vCPU equals one core license. Would make sense to use this with my 2016 SQL Server VMs.
2. From that website - A minimum of four core licenses is required for each physical processor on the server - so even if i only wanna use 2vCPUs for a single 2016 SQL server - does this mean i need to buy four core licenses to cover that single VM as it sits on a physical Esxi host?
3. If, like nearly all enterprise IT depts, i use DRS to loadbalance our VMs in a cluster (which is normal) - would i technically have to license the number of physical Esxi hosts as well - in that VM cluster - as the SQL Server will migrate around as cluster resource usage always changes?
4. Is Software Assurance required in a virtual environment to cover migrating around Esxi hosts in a cluster?
Thanks all !
Again, talk to a knowledgeable vendor, even MS itself if you need to. SQL Server pricing is too complex now to try to wing it on your own, even with Google's "help" / EE expertise.