Is it worth moving the SQL Server system databases master, model and msdb from the default install path on the main OS hard drive over to their own drive?

I've already moved TempDB on to 2 separate drives one for the log file and one for the data file and am just wondering if its worth doing the same to the other system database or if this is overkill and will see little to no benefit?

| improve this question | | | | |

I see not reason for moving them at all -- they are small DBs that are cached in memory pretty much all the time. You are not going to make changes very often in those DBs (writes) to have them moved to another drive to gain some additional performance.

| improve this answer | | | | |

It depends. There are some cases where you might want to put them on a dedicated drive (which I've done once or twice). Usually this is in a clustered setup where you can't put them on the OS drive, and you don't want them on the drive with the user databases on them, so a separate drive it is.

| improve this answer | | | | |

I couldn't think of any reason to move your system databases to dedicated drive.

It's good (and recommended) practice to dedicate drives to TempDB and all user databases - as a very general directive.

| improve this answer | | | | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.