Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Maintenance Plan on System Databases?

Author  Topic 

denis_the_thief
Aged Yak Warrior

596 Posts

Posted - 2010-09-07 : 09:56:37
Currently, our Maintenance Plans exclude the System databases (i.e. Master, TempTB). Is there any merit to adding these Databases for Rebuilding Indexes, Update Statistics etc...?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-07 : 12:30:22
You should only perform a full backup on the system databases, except tempdb which doesn't require any maintenance.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

denis_the_thief
Aged Yak Warrior

596 Posts

Posted - 2010-09-07 : 13:50:17
Thankyou.

But then would the stats get updated and Indexes re-built for Master Database automatically? If not, wouldn't it become inefficient like any other Database would?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-07 : 14:03:54
You shouldn't be storing much in master or the other system databases, so statistics/index rebuilds shouldn't matter. If performance ever becomes critical in the system databases, then you've got a bigger problem.

Auto create/update stats is enabled, so that really should be enough.



Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-09-07 : 14:08:30
We take a file-level-copy of Master & MSDB as part of server-startup - i.e. before SQL Service starts. And we store the last N copies (I've forgotten how many that is, but it was designed to ensure that we were likely to have "at least one fairly old one" even if we had to do several reboots in a row. (They just get renamed round-robin each time).

Thus if we ever had a total corruption of Master we could copy-back the most recent copy-file, and then (once we got the service running again) restore the most recent backup.

We used to copy the file "manually" when we remembered, but it is important to refresh the copy after Service pack upgrades, and we always take the opportunity of installing a service pack to reboot ...
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-07 : 14:10:17
We just rely on our database backups.

I realize that a file copy would be fastest/easiest to do the restore, however needing to restore a system database is very, very rare so a database restore would be fine.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-09-07 : 14:15:32
<Knock on wood> we've never had to use the System DB copies.

My rationale is that they are tiny (so don't take up much disk space / time on a reboot etc.), but if we had a catastrophic failure of Master the messing around to fix it, restarting the Service in Single User (and looking up the DOCs to work out how, as I only do that once-in-a-blue-moon), plus the harassment from Client / Colleagues to "Get the thing upright and quickly) I think makes the task worthwhile.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-07 : 14:20:01
We'd rely on our DR site in a situation like that. We can failover to our DR site in seconds and then can take time fixing the primary site.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -