locked
SCOM 2012 R2 SQL DB State monitoring RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey all,

    Am really scratching my head here because I cannot find anything anywhere that has my issue.

    We have SCOM 2012 R2 and as a test I have been doing various bits and pieces to test SQL DB monitoring.

    If I delete or put a database offline or anything along those lines it takes nearly an hour before an alert will come through.

    Is there something I am missing?  Any help would be GREATLY appreciated.

    Thanks all

    Shane

    Tuesday, September 26, 2017 11:27 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shane,

    >>If I delete or put a database offline or anything along those lines it takes nearly an hour before an alert will come through.

    It would be caused by the default state checking interval "3600" seconds:

    You can override this monitor .

     

    Best Regards,

    Elton

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Elton_Ji Wednesday, September 27, 2017 7:19 AM
    • Marked as answer by ukkaapie Wednesday, September 27, 2017 12:23 PM
    Wednesday, September 27, 2017 7:17 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    First, ensure you have the SQL management pack(s) for your version of SQL imported to your management group.  Deleting/Detaching a database will not necessarily generate an alert, but the 'Database Status' monitor will tell you if it's offline/suspect/recovery, but if you want tighter monitoring you'll need to override the interval.

    Overrideable Parameters

    Name

    Description

    Default Value

    Alert Priority

    Defines Alert Priority.

    Normal

    Alert Severity

    Defines Alert Severity.

    Error

    Enabled

    Enables or disables the workflow.

    Yes

    Generates Alerts

    Defines whether the workflow generates an Alert.

    Yes

    Interval (seconds)

    The recurring interval of time in seconds in which to run the workflow.

    3600

    Synchronization Time

    The synchronization time specified by using a 24-hour format. May be omitted.

     

    Timeout (seconds)

    Specifies the time the workflow is allowed to run before being closed and marked as failed.

    300

    B. Wright

    • Proposed as answer by B. Wright Tuesday, September 26, 2017 2:18 PM
    Tuesday, September 26, 2017 2:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shane,

    >>If I delete or put a database offline or anything along those lines it takes nearly an hour before an alert will come through.

    It would be caused by the default state checking interval "3600" seconds:

    You can override this monitor .

     

    Best Regards,

    Elton

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    • Edited by Elton_Ji Wednesday, September 27, 2017 7:19 AM
    • Marked as answer by ukkaapie Wednesday, September 27, 2017 12:23 PM
    Wednesday, September 27, 2017 7:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Elton and B.Wright... thanks heaps for your answer.

    This has done exactly what I need it to do.

    Many many thanks

    • Edited by ukkaapie Wednesday, September 27, 2017 12:24 PM
    Wednesday, September 27, 2017 12:23 PM