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.
| Author |
Topic |
|
admin001
Posting Yak Master
166 Posts |
 Posted - 2007-10-15 : 13:04:32
|
| Hi,I would like to have your expert views on alternative methods on monitoring SQL 2000 servers without using any external software. I know tools could be the quickest way to annwer this query , however I am looking at some thing really different. We have approx 40 SQL servers out of which roughly 20 are production and their equivalent 20 are DR servers. We have written customised scripts to ship the backup and logs on a daily basis from prod to DR servers and we prepare a daily textpad report highlighting main issues that went wrong and needs to be fixed.The scripts run daily on all SQL servers and checks for failures for DB backups, txn log backup , log shipping to DR server and restore on DR servers as well and it writes the output to a text files in one folder . Then we run one monitoring script from our workstations which picks up the error messages from the output files on the Server. The pain here is that is we have to prepare a daily manual report ( which involves lot of cut and paste ) to prepare a final report which is too time consuming and we are looking for some kind of automation to achieve the expected report. Is there any utility where we could simply look for the error messages and the tool can provide us a final formatted report in PDF or word format and we can use that final output to rectify the failed jobs ? We are trying to figure out some ways to do it since it is difficuilt to throw away the existing setup and migrate to a new monitoring software right away. Any suggestions or alternative strategies can be of great help to us. Thank you very much. |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-15 : 13:26:47
|
| My general view on this is that processes so insert rows into a "logging" database (so Start & Finish, and also Success as well as Error messages).Then something else should check the logs to see that all the expected messages are there - i.e. the Backup DID start and DID finish and DID NOT produce any errors AND completed BETWEEN 10 minutes and 20 minutes.Then if any of these criteria are not met it should output some sort of alert.That way you only have to worry about the exceptions ..... and you can scale it up for as many systems as you need to support.Kristen |
 |
|
|
admin001
Posting Yak Master
166 Posts |
Posted - 2007-10-16 : 05:49:54
|
| Thanks for your inputs. Btw I was thinking whether has anybody installed Microsoft Operations manager 2000 by any chance. I believe it is suppose to check the routine errors like backup failures, space availability and agent related issues. Perhaps this could be one way to monitor and then put soemreporting stuff on it to extraxt the reports. I am not sure how this MOM 2000 works. Thanks once again. |
|
|
|
TonyTheDBA
Posting Yak Master
121 Posts |
Posted - 2007-10-16 : 07:37:15
|
| I Installed MOM Once . . . . . Well 5 0r 6 time actually, never got it to work properly though. That could be our Network / Firewall configuration though-- RegardsTony The DBA |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-16 : 07:55:04
|
| I think Tara has used it. Tara? |
|
|
|
|
|
|
SQL server automated error reporting.