|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 6:46 AM
Points: 38,079,
Visits: 30,373
|
|
For recoverability, definitely. For performance, maybe. What's the IOPS for the array? What's the required IOPS for the app?
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, October 09, 2012 5:55 AM
Points: 2,
Visits: 8
|
|
| Not sure. So far this is theoretical. but I'll find out. For now assume reasonably modern equipment.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Today @ 6:33 AM
Points: 804,
Visits: 5,252
|
|
Consider windows page file, tempdb, db files, and log files as candidates to move. Also part of the picture is as others point out, what kind of IO patterns there are. And if this is a dedicated SQL server, or runs other applications. There also is a balance of cost to service level and recoverability, unless budget is of no concern.
If you have a test environment, and a few extra old disks available (nothing fancy needed), you could set up and move the files. Then run some load tests.
Lots of things to consider. I tend to get some local disk for some activity, but have some SAN partitiions carved out for those I need throughput and recoverability on. You could also search for some of the whitpapers on SQL Server Performance. They have some very good information, although these tend to be more for those where budget does not play a factor. I don't have the neeed to load 1 TB in less than 30 minutes. But it is interesting to see what it takes.
|
|
|
|