Jay Graves

My feedback

  1. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jay Graves commented  · 

    Agree as more information (server/database name) will allow us to react faster and route alerts to correct Slack team. Thanks!

  2. 103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Jay Graves shared this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Jay Graves shared this idea  · 
  4. 113 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jay Graves commented  · 

    I found a custom metric for a single long running job. However, what we need is a way to alert for SQL Agent jobs that are running beyond a designated time (similar to the long running query metric built in). The "unusual duration" alert doesn't quite do what we need. Hopefully someone knows how to make this a custom metric. If not, consider a feature request!

    Jay Graves supported this idea  · 
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Jay Graves shared this idea  · 

Feedback and Knowledge Base