Anyone have any good feeling on how to arrange the underlying disk configuration for a VM (Hyper-V) implementation of SQL Server vs installing straight up on the hardware?
For a native Install, best practices say to put the logs on separate spindles from the data spindes, but what about in a virtual environment? Whereas the VM has virtual disks, we could create separate log .vhd and data .vhd and put those on separate spindles as before, but why not just stripe all your available disks and put the log and data virtual drives on the same set? Hypothetically, the more spindles in the stripe the faster the response and more IOPS, so we could just put both files on the same set. The Host machine would be acting as sort of a SAN.
The server we have is moderately busy, no problem with IO performance (logs and data currently on separate spindles) or CPU or memory pressure. The goal is to have more flexibility in maintenance, being able to clone or move the VM elsewhere, and possibly put another VM on the box to better utilize the hardware. It seems that creating one large striped drive in the host machine would allow us the full use of all available drive space without much impact on performance. The alternative is losing out on about 1/3 drive space just to hold smallish log files.
Server config is Windows 2012 R2 OS, SQL Server 2016. 6 drives in RAID 10 for all of logs tempdb and data -OR- 2 drives in RAID 1 and 4 drives in RAID 10 for tempdb and data.