Hi All,
I am about to start setting up an SQL server on Hyper-V for an ArcGIS Server. I have done a fair bit of reading on the subject of drive configuration and generally, people seem to agree that OS, Data, Logs and TempDB should all be on different drives as they have different performance requirements.
The hardware we have for the new server has 4 x 2 TB SAS SSDs in RAID 10, for VM storage and a 240GB RAID 1 for Hyper-V. The 4 disk array is currently configured as one big drive in Hyper-V.
Now, I can setup the SQL server to have separate virtual disks for OS, Data, Logs and TempDB, however, this seems to not really achieve much as all the virtual disks will be stored on the same SSD array.
I have seen some info about configuring SQL in Azure which seems to indicate that it is OK to put the Data and Logs on a Premium SSDs and TempDB on another (non-persistent) drive. I have also seen some people putting forward if you are on an SSD array the disk configuration becomes a lot less important.
If the case is that on this HW, I don't need to create a separate virtual disk for each of Data, Logs and TempDB, then I would prefer to simply have 2 drives - OS (including SQL server app) and Data (for Data, Logs and TempDB).
I'd love to hear any suggestions on what might be the best setup with the HW I have in your opinion.
Thanks
Regards
Mike