|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 11:32 PM
Points: 68,
Visits: 169
|
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 11:32 PM
Points: 68,
Visits: 169
|
|
Hi all,
There appears to be a dead image in the article, so I've posted the image here. This is what our Failed Jobs report will eventually look like. It has three buttons that will retrieve the relevant logs on the server. Remember, all the work in the previous articles is not just for the one report. It's just part of the initial setup. After this, you'll be able to create a report from anything SQL Server holds in it's system tables for all your servers, with minimal effort.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 8:49 AM
Points: 34,
Visits: 152
|
|
We've been using a different variant on this, first there's a job that runs every hour that mails us the results of the following view:
SELECT CONVERT(DATETIME, RTRIM(H.run_date)) + ((H.run_time * 9 + H.run_time % 10000 * 6) + H.run_time % 100 * 10) / 216e4 AS run_date, J.name, H.message, H.run_duration, H.server FROM LINKED_SERVER_NAME.msdb.dbo.sysjobhistory AS H INNER JOIN [SRV-NAV01].msdb.dbo.sysjobs AS J ON H.job_id = J.job_id WHERE (H.step_id = 0) AND (H.run_status = 0)
This also works like a charm and is easy to set up. You can either pro-actively monitor the view, or have a job schedule mail these results to you (like we did). You can simply UNION select any production server (linked) that you'd like or take it one step further and use CLR to enumerate through all available servers.
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Thursday, February 21, 2013 8:38 PM
Points: 54,
Visits: 68
|
|
Shameless plug : please see the project on http://www.codeplex.com/sqlconsolidate - it does the same on a console application * and can export data to csv/xml/ email / database
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, May 24, 2010 12:11 PM
Points: 8,
Visits: 108
|
|
| COOL STUFF SO FAR. WHEN WILL YOU GET INTO THE .NET STUFF
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 11:32 PM
Points: 68,
Visits: 169
|
|
LostFromTheStart (4/24/2009) COOL STUFF SO FAR. WHEN WILL YOU GET INTO THE .NET STUFF
Was going to do it in article 5, but people are getting restless, so going to try and do it next.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525,
Visits: 617
|
|
Excellent series! I especially like that I can build on this type of infrastructure and extend it further (and don't have to pay for expensive 3rd party tools ).
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, March 15, 2013 9:20 AM
Points: 18,
Visits: 113
|
|
| Great stuff so far. When will part 4 be posted?
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Wednesday, September 26, 2012 11:32 PM
Points: 68,
Visits: 169
|
|
Hi Gary,
I'll try and finish the next three articles this weekend and publish them on my site thebuddingdba.com, Monday. I'll send them off to SQLServerCentral.com but I think there is a three or four week wait.
Kind regards
Drew
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, March 15, 2013 9:20 AM
Points: 18,
Visits: 113
|
|
Thanks Drew, we're looking forward to the new articles. Quick question: We have set up links to several servers that just have the default instance installed and it works great...however, how can we set up servers with named instances? For example, we have a SQL Server farm with 9 named instances. How can we link to each of the named instances for monitoring?
Thanks.
Gary and Ann
|
|
|
|