Moving heavy use db's to their own files

  • I have a 3rd party app that is comprised of 9 databases. 2 of them are heavily used the others more for reference. This is an OLTp application. Anyone seen great gains out of moving heavily used db's to their own files/arrays.

  • Not only would you get a gain out of that, if the 3rd party allows it you could get an even bigger gain by putting tables on one disk and indexes on another disk. It depends of course upon how big the structures are whether it's worth the disk expense or not, but moving I/O into isolation will often boost performance.

  • Simply moving them to a seperate file will get you some, very moderate, performance gains, but moving them to their own disk will help a ton. But, it's still best to be sure that you're seeing IO bottlenecks and not issues elsewhere.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • If this is a SAN, try to be sure the LUNs are physically separate from the other disks. If it's DASD, I'd ask for a new controller as well, move them to a new controller, new disk arrays.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply