locked
Disable monitoring SQL jobs RRS feed

  • Question

  • Hi,

    Is it possible to disable or override monitoring of one or several SQL jobs that runs under the SQLSERVERAGENT?

    Please advice.

    Best Regards,

    Sport
    Tuesday, January 12, 2010 8:49 AM

Answers

All replies

  • All agent jobs is a 'SQL 200x Agent Job' class instances so yes, you can override monitors you don't need for particular job instance (override for a specific object of class).
    http://OpsMgr.ru/
    Tuesday, January 12, 2010 9:07 AM
  • I think this depends on the monitor you are using. There are a number for monitoring SQL jobs - long running jobs \ failed jobs etc. 

    Some of the monitors are targetted at SQL Agent and so you can't override for a specific job. Some are targetted at SQL Agent job and these you can override on a per job basis.

    I don't have a system to hand to double check but if you go to authoring, monitors and scope for SQL200X agent and SQL200X agent jobs you'll be able to drill down and see each of the monitors.

    Cheers

    Graham


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Tuesday, January 12, 2010 9:24 AM
  • Hi Alexey,

    And thank's for a swift reply, but I think I need a little bit more guidence.. :-)

    Under you can see an alert from a SQL job that has failed, and I want to disable monitoring of this job. So if I go to Overrides -> Override the Rule -> For a specific object of class: SQL 2005 Agent, it shows the all the SQL Agents running in our environment. Where do I go wrong here?


    A SQL job failed to complete successfully

    Source: SQLSERVERAGENT
    Path:
    srv-win-dba-005.shdir.no\MSSQLSERVER\SQLSERVERAGENT
    Alert Rule:
    A SQL job failed to complete successfully


    Alert Description Source:

    SQLSERVERAGENT SQL Server Scheduled Job 'SRV-WIN-DBA-005-GisbasTest-Gisbas-SRV-SOS-002\GISBASOS-7' (0x77982DC88FB1FB45B7512B3E4C40C675) - Status: Failed - Invoked on: 2010-01-12 10:34:00 - Message: The job failed. The Job was invoked by Schedule 39 (Replication agent schedule.). The last step to run was step 3 (Detect nonlogged agent shutdown.).


    Sport
    Tuesday, January 12, 2010 9:54 AM
  • Hi

    Please check out my response above - as this rule has been targtted to SQL Agent, you cannot override at the job level. If you follow my post above, you will see there are monitors available that are targetted at the individual job.

    Cheers

    Graham


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Tuesday, January 12, 2010 10:24 AM
  • Hi,

    If I go to authoring, monitors and scope for SQL200X agent and SQL200X agent jobs I can't see or drill down to any specific job.

    So, in our scenario, there's no possibility to disable monitoring of a SQL job like we need to do?

    Any other way to solve this?

    Brgds,
    Sport
    Wednesday, January 13, 2010 11:43 AM
  • Hi

    Not sure I understand your response - the monitors won't list the actual SQL jobs. But you will see monitors under SQL200X agent and SQL200X agent job. The monitors that are targetted at the SQL Agent can't be overriden by sql job. The ones that are targetted at Agent job can.

    See this post for further details which gives an actual example:
    http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/a2919bb3-1184-46d7-9b54-ddda5c34dac8

    Let me know if that helps (or just confuses!).

    Cheers

    Graham
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Wednesday, January 13, 2010 11:58 AM