Azure VM disk per drive SQL server
inna last edited by
On an Azure VM, does it matter if I partition a large disk into multiple drives (to hopefully be more contiguous - not sure if it'd matter virtually) where if space is needed, it'd then need to be a dynamic allocation (as far as OS)? Or should I generally stick to a disk per drive when expansion would seem necessary?
Usually in Azure Vm you should pool disks (P30 or P40) to achieve higher level of troughput. If you need different drives i suggest creating differend storage pools.
This way gives you better IO performance that usually is great for databases, but gives you difficulties to enlarge drives. Enlarge drives inside a storage pool is not possible, but you can add more disks to the pool as an alternative.