New SQL 2016 server install on Virtual server--windows . Is it still necessary for a separate drive for tempdb? I am thinking of separate drives for data and log.
Inputs appreciated. Windows server 2016
Read through this article and you should get a better idea. I'm more of a split drive kind of guy. App on primary drive, data on another drive, logs on third.
When you create a virtual server you assign one or more virtual hard drives to go with it.
Depending on how you ask for the virtual drives, they may all be on the same drives on the physical disk subsystem.
Unless the administrators of your virtual environment can ensure each logical drive in on different physical drives, splitting them up on the VM side doesn't get you anything.
--Unless the administrators of your virtual environment can ensure each logical drive in on different physical drives, splitting them up on the --VM side doesn't get you anything
In your opinion, Should I ask the virtual admin to put each logical drive on a different physical drive(if that is not the case already) or better put is it worth it at all splitting log and data files for SQL Database in the VM world?
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-performance