Thanks for the advice Steve. Please see my comments below:
The way I've done this is I have every server monitor itself. Make a small db (worst case, stick some tables in msdb) and query for backup status, jobs status each day. Store that information at each server. Make this a part of build status. I went so far as you also make a "report" table that merely stored the day's reports in a series of rows I could easily read with a query.
Just to clarify:
1) Create a scheduled job on each server to gather information about job and backup statuses and store them in a localdb or as you said, worst case, a couple of tables in MSDB.
2) Create an SSIS package on the central server that will loop through the list of servers to poll the backup information and store it in the central database for reporting purposes.
Sorry but I’m confused as to why the need for the local data on each server? Why not get the information straight from the MSDB as my SSIS package loops through each one?
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn