September 9, 2011 at 8:38 am
Hello,
Do I need to run Integrity/Optimization jobs system for temp.
Also what do I need to check for system databases when I run Integrity/Optimization jobs system.
Thank you
September 12, 2011 at 5:35 am
Yes and yes. If the system databases go offline, you're just as in trouble as if the user database went offline.
"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
September 12, 2011 at 5:58 am
I'd actually say it's worse, especially in a multi db environement.
Imagine losing 1 out of 100 dbs. It's annoying to very problematic, but if ALL of them go offline untill you can rebuild / repair the server then you're in a world of hurt.
September 12, 2011 at 5:59 am
Ninja's_RGR'us (9/12/2011)
I'd actually say it's worse, especially in a multi db environement.Imagine losing 1 out of 100 dbs. It's annoying to very problematic, but if ALL of them go offline untill you can rebuild / repair the server then you're in a world of hurt.
True. I guess I was being too gentle.
"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
September 12, 2011 at 6:04 am
Grant Fritchey (9/12/2011)
Ninja's_RGR'us (9/12/2011)
I'd actually say it's worse, especially in a multi db environement.Imagine losing 1 out of 100 dbs. It's annoying to very problematic, but if ALL of them go offline untill you can rebuild / repair the server then you're in a world of hurt.
True. I guess I was being too gentle.
As always, it depends!
The realy issue is that most people don't train for that (myself included... been on the todo list for too long now).
And when it happens you just don't know what to do.
September 12, 2011 at 6:21 am
Note that you can't back TempDB up, and trying index rebuilds will be a waste of time (if even possible). You can run CheckDB, but any problems you find will require restarting SQL to fix.
That's just for TempDB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 12, 2011 at 6:36 am
Thank you very much, so master,msdb,model I will check for:
Check integrity,reorginize index,rebuild index right?
September 12, 2011 at 6:37 am
Krasavita (9/12/2011)
Thank you very much, so master,msdb,model I will check for:Check integrity,reorginize index,rebuild index right?
BACKUP.
Integrity is also VIP. Index maintenance is less of an issue.
September 12, 2011 at 6:44 am
Index rebuilds are only needed for MSDB. Master has no user tables, model should not ever have data changing fast enough to require rebuilds.
Edit: And besides, you should never reorganise indexes then rebuild. Complete waste of time, do one or the other.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 12, 2011 at 6:47 am
Thank you,
So for system database:
Backup, check database integrity (master,model,msdb),rebuild indexes(msdb) is this correct?
September 12, 2011 at 6:49 am
Krasavita (9/12/2011)
Thank you,So for system database:
Backup, check database integrity (master,model,msdb),rebuild indexes(msdb) is this correct?
Yes. I actually use this script to pick out which indexes need work. It goes through the system dbs as well.
I can say that I never have any work to do in model... master maybe 2-4 times / year. Msdb maybe once every 2-3 months.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply