Microsoft SQL server on VMware environment
We have a VMware cluster with 17 physical esx, for a total of 420 cores. Out of this, 2 esx host the SQL instances, with a total of 48 cores.
As vMotion is activated, Microsoft will ask to license the 420 cores, except if we isolate the 2 SQL esx.
My question is about cluster segregation, i.e. Oracle is quite strict on such way of working. What could Microsoft accept as VMware cluster segregation. We can only organise a LUN masking on SAN, desabling other esx to access MS SQL data on the storage, is it enough? If not, we should then acquire additional storage and isolate everything in a vLAN.
We can also simply create and additional vSphere specific to SQL server but it's not a barrier for vMotion.
Does somebody has experience on what could be acceptable to avoid licensing a full global cluster?
Open Jun 10, 2018 - 10:16 PM
Microsoft SQL Licensing, VMware