Unsolved
This post is more than 5 years old
61 Posts
0
705
March 9th, 2012 05:00
Leaving tempdb out of the resource group
Microsoft supports having tempdb on a non-clustered disk. Is anyone actually doing that?
For some installations where cluster enabler is in use, this could represent a significant savings on bandwidth, and could boost performace in the case of synchronous replication.
No Events found!
mmcghee1
18 Posts
0
March 9th, 2012 13:00
I haven't tested this yet, but to your point, I'm expecting leaving tempdb on non-replicated/non-clustered disks to be a recommended practice with cluster enabler and SQL Server 2012 should bandwidth and sync performance be a concern.
One downside I can think of is the administrative overhead of making sure every node has the same storage configuration and mount points for their tempdb location. Also, depending on the number of nodes and the planned size of tempdb, there could be a lot more storage required and now dedicated to tempdb seeing that the LUNs are no longer shared.
I've yet to speak with a customer about this, but I'd be happy to test or demo (with SRDF) if someone has a customer request.