Hey everyone! So, my colleague accidentally resized the wrong disk of our SQL Virtual Machine in Azure. Instead of extending the correct data disk, they ended up resizing the underlying standard VM data disk. Now, I'm facing an issue where the VM object shows a disk size of 512 GB, but the SQL Virtual Machine only reflects 255 GB in storage details and even in Windows. This hasn't changed. I'm looking for advice on how to get everything back in sync since we can't revert the resize. Has anyone run into this kind of issue before? Any tips would be really appreciated!
1 Answer
It sounds like your data disks might be part of a storage pool since some SQL Server VM templates do that automatically. If that's the case, just extending the disk won't work. You would need to add another disk of the same size to the pool. Have you tried doing an OS-level extension? What did that show?
Yeah, I realized it was in a pool, but I only have one disk per pool right now.