Checking the Job Status on Multiple Servers

  • Comments posted to this topic are about the item Checking the Job Status on Multiple Servers

  • nice article, but is there any method other than linked server to connect to various servers.

    "Keep Trying"

  • I always seem to get this error:

    Msg 7357, Level 16, State 2, Line 1

    Cannot process the object "exec msdb.dbo.sp_help_job". The OLE DB provider "SQLNCLI" for linked server "JOB_TSSQL6" indicates that either the object has no columns or the current user does not have permissions on that object.

    JOB_TSSQL6 is the name of my linked server.

  • Just to be completely open about all this, I am employed by BMC Software. Having said that, I would like to suggest using an Enterprise Job Scheduler, like BMC CONTROL-M, that provides the ability to run SQL Server jobs such as sql scripts or stored procedures. If you use CONTROL-M, you get centralized job status monitoring from single management console across any number of database instances. You get all the infrastructure that has usually been built to manage scheduling such as 24x7 staffing, alerting via the scheduling console, email, automatic incident creation in Remedy, Service Desk Express, HP Service Desk and other such tools, ability to define automatic recovery actions and simple and intuitive dependencies between database tasks and other batch such as running your apps, file transfers, managing ERPs like SAP, Peoplesoft or Oracle eBusiness Suite, etc.

    You don't need to create additional databases to track anything because CONTROL-M does it all for you. You don't need to write and maintain scripts and perhaps best of all, DBAs can spend their time administering databases rather than doing job scheduling.

  • Is it not possible to run stored procedures through a linked server? I have RPC set to true.

  • You can use powershell to execute a script on multiple servers. This article shows how to do this, populating an excel worksheet with information on failed jobs:

    I modified that script, adding sheets showing backups, database data file space, and recent lines in the error log, filtering out mundane messages. Failed jobs, failed backups and data files with less than a certain percentage of free space are in red.

    I then scheduled a job executing this script each morning before I come in, resulting in a quick summary of our servers.

  • Hi , its a very cool article.

    Can't we get the information of the jobs running under master server.

  • Hi,

    Thanks for your comment. Yes you should be able to get the jobs from the master server too. Pls check that the master server is listed in the sysservers table.



  • I am getting the following error when I try to run the usp_help_job_status stored procedure.

    Msg 208, Level 16, State 1, Procedure usp_help_job_status, Line 17

    Invalid object name 'mondb.dbo.job_status'.

    What am I doing wrong?:-D

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply