February 19, 2016 at 2:38 am
I know its best practise (and our standard) to split SQL Data, Logs, TempDB and backups onto different drive letters. Is there still a performance advantage of doing this in a VM environment if we just have 1 raid 5 pool of disk?
I was planning on partitioning our SQL database and splitting out high read tables, high insert\updated tables, static data into separate file groups and having them on separate disks, but if a performance benefit of using multiple disks cannot be achieved due to us having just one pool of storage, there is clearly no point in us doing it.
Any advice would be appreciated
February 19, 2016 at 2:46 am
SQLAssAS (2/19/2016)
Is there still a performance advantage of doing this in a VM environment if we just have 1 raid 5 pool of disk?
No.
There may be a management benefit (TempDB growing out of control can't affect the user DBs if they're on separate logical drives), but that's about it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply