January 13, 2009 at 8:45 am
What sort of standard day to day maintenance are most common in maintaining a healthy SQL Server?
Currently I'm doing backups, doing an integrity check, and rebuilding indexes/updating statistics as needed. Anything I'm missing?
Also, while the maintenance plan wizards make this sort of thing easy, I still have a few questions. Ideally, I'd like the server to only email me if there's a problem. While I can have it only email me if a maintenance job fails to run, I don't think that's quite what I want. For example, the job that checks integrity could successfully run, but it could find a problem. Does that trigger the "when the job fails", if an integrity issue is found? Or does it consider the job to check the integrity was successful?
January 13, 2009 at 9:54 am
Create a maintenance plan with Check Database integrity task ..and put a notification on the job that when it fails it will send you an email..Whenever the DBCC Checkdb gives an error you will be notified.
January 13, 2009 at 1:49 pm
Use SSIS for setting up maintainance jobs. It gives you a whole lot of options. Even if you create a maintainance plan it will internally create a SSIS packages to get that task done.
Just go through the creating a package for Maintainance purpose and you will find a lot of options.
Hope it helps.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply