June 10, 2020 at 6:36 am
Hi everyone. I asked this question in dba.stackexchange.com but unfortunately I wasn't satisfied with answers so I decided to ask here.
Question: is there any point of moving tempdb files into different disk drive if all LUNs are from the same RAID pool?
According to best practices, it is recommended to move all tempdb (not just tempdb) files into different physical disk. I have a virtual server which had originally 4 LUNs from the same RAID 10 pool. By the help of volume manager, I converted those 4 LUNs into 4 different volumes. Now the question is, will it make any difference in terms of performance by moving tempdb into separate volume, if those volumes are actually originated from the same raid pool?
June 10, 2020 at 12:57 pm
Yes on keeping it on a separate assigned drive letter. I find that it's important to keep TempDB associated with a different drive letter than all the rest so that someone's nasty code mistake doesn't cause TempDB to fill an entire data drive. It just keeps things simpler.
As far as performance goes, it you can put TempDB on Raid 1/0, it'll be faster. Of course, not much difference if it's on SSDs. Just be aware that TempDB is a bit tough on the lifetime of whatever SSDs you put it on.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 10, 2020 at 4:54 pm
In addition to what Jeff noted, if you get to move this to different hardware or change the makeup of the LUN, having a different drive letter provides some abstraction.
June 10, 2020 at 5:30 pm
Thank you guys for your valuable time and answers. I am now satisfied with answers.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply