This is the title of the last of a serie of good articles from SQL Server Central.
Checking all instances of SQL Server every morning is one of the best ways that a DBA can ensure that the databases are available, jobs have run without a problem, and connections are being made. However, connecting to each instance of SQL Server is both time consuming and impractical. Using the SQL Overview package and the reports described in this article, the need to connect to each instance is virtually eliminated! These articles eight reports are scheduled to run every morning to "check" on potential problems since the previous day's run. An e-mail is sent with the results of the "check". You now spend your time resolving issues instead of manually reviewing each server.
Checking all instances of SQL Server every morning is one of the best ways that a DBA can ensure that the databases are available, jobs have run without a problem, and connections are being made. However, connecting to each instance of SQL Server is both time consuming and impractical. Using the SQL Overview package and the reports described in this article, the need to connect to each instance is virtually eliminated!
These articles eight reports are scheduled to run every morning to "check" on potential problems since the previous day's run. An e-mail is sent with the results of the "check". You now spend your time resolving issues instead of manually reviewing each server.
It's here : http://www.sqlservercentral.com/articles/Administration/63042/
List of Report Jobs: DBA-SQL Overview - Report Databases Missing Backups (Contains both database and log backups missing reports) DBA-SQL Overview - Report Drives Very Low on Space DBA-SQL Overview - Report Errorlog Messages DBA-SQL Overview - Report Instances Recently Started DBA-SQL Overview - Report Job Failures DBA-SQL Overview - Report Large Log Files DBA-SQL Overview - Report Table Refresh Errors
List of Report Jobs: