February 22, 2011 at 12:07 pm
We currently have sql 2005 installed in a SAN environment, with the system partition installed on the host using vmware and a secondary partition on SAN allocated to all user databases. Should the system databases be moved to the secondary partition with the other databases? In the event of a crash will the system databases be out of sync with the other databases? We are currently backing up the vm M-TH, we are backing up the individual databases with a full backup weekly and incremental backups M-TH.
February 22, 2011 at 12:26 pm
Overall there should be no reason to move them unless you just want to. As long as you are doing full backups of the system databases on a regular basis (AND testing them) you should be fine in the event of a crash. They are not really "synced" with the user databases. The master database stores all the information about the user databases so you might back this up more frequently than the other system databases if a large number of changes are made to user databases.
The tempdb is a database that changes often and is not required to be backed up. DBAs usually place this on it's own drive for performance reasons. It just depends on the load your instance has on it if you want to do this or not.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply