Azure VM disk per drive SQL server

All we need is an easy explanation of the problem, so here it is.

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?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

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.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply