Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
up vote 4 down vote accepted

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.

share|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.

share|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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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