3 ms·
> This is still light years ahead of Azure (and to a less extent GCP), where even compute services will not necessarily work with one another. You can't use th
by jiggawatts 6y ago
> This is still light years ahead of Azure (and to a less extent GCP), where even compute services will not necessarily work with one another.
You can't use the SQL Server Virtual Machine extension on an Azure VM to extend the disks if the VM size is one of the AMD EPYC CPU types.
During the support call, the Microsoft tech shared a screenshot of the source code for the SQL VM extension, and it had a switch statement that decides if each feature is "supported" or not.
Let that sink in: Microsoft literally hard-codes their VM-size-to-feature lookups in probably thousands and thousands of places with huge switch statements full of code like this:
case "Standard_M416ms_v2": return false;
case "Standard_M416s_v2": return false;
case "Standard_M64ls": return true;
case "Standard_M64ms": return true;
This is their standard coding practice.
So next time you try a new VM size or type, don't be surprised if things randomly don't work or "aren't supported" for mysterious reasons...