Part 4 of our series take us to Visual Studio and the world of .Net. We will display our failed jobs report in a web browser using Visual Studio; a to the point, sweet and sassy guide to using Visual Studio Web Developer.

We're ready to create our first report, the Failed Jobs report. This report will display all (if any) failed jobs on our 15 gazzillion SQL Servers, and allow us to further drill down to each server's logs to locate the cause of the failures without having to connect to each via Management Studio.

Are you now thinking, "I could do with some of that". Have you too established that you need to centralize your monitoring of SQL Servers, relieved to know that you are not the only DBA having to cope with so many. We've discussed the principles behind a method for centralized monitoring, the SCOME technique, so let's now start setting this up by creating the necessary linked server objects.

This article describes how you can centralize the monitoring (Failed Jobs, Unrun Backups, T-Log size, Cyclic Test Restores, Cyclic ReIndexing, Disk Space and Disk Space History and so on) of all your SQL Servers (and their databases) from an ASP.Net site on your local machine... AND without the use of third party software. Once setup, you will know daily what is running, what isn't and why. You'll be on top of every aspect of monitoring and regularly find yourself informing other members of the department of errors and warnings in their areas well before they are even aware of it.