Skip to content

Mike Cutts

My feedback

1 result found

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Daniel Rothig responded

    For your usecase I recommend modifying the maintenance window metadata instead:

    UPDATE s SET MW_IsEnabled = 1, —or 0 to enable alerts again MW_Start=0, —midnight MW_Duration=864000000000, —24 hours MW_Monday = 1, MW_Tuesday =1, MW_Wednesday=1, MW_Thursday=1, MW_Friday=1, MW_Saturday=1, MW_Sunday=1 FROM [settings].[SqlServers] s INNER JOIN [settings].[Clusters] c ON c.Id = s.ParentId WHERE c.Name = ‘hostname’ AND s.Name = ’’ —Set to SQL Server name or leave empty for unnamed instances

    A restart of the base monitor service will be required after the change

    An error occurred while saving the comment
    Mike Cutts commented  · 

    Thanks for the suggestion. However, we were wanting to be a little more granular than that. We will have databases on an instance where we may not want to perform index maintenance against them, but may want to perform a backup. Therefore, just enabling and disabling a maintenance window (if I understand it correctly) might not work as it would disable all alerting for an instance.

    Feel free to correct me if my understanding is wrong on this one.

    Mike Cutts shared this idea  · 

Feedback and Knowledge Base