SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Monitoring for Non Existent Events


Monitoring for Non Existent Events

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)

Group: Administrators
Points: 150458 Visits: 19454
Comments posted to this topic are about the item Monitoring for Non Existent Events

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Gary Varga
Gary Varga
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27655 Visits: 6556
See as so many of us will have studied state machines in one way or another, it remains astounding that so many of us, so many times do not setup monitoring to cater for all states. This is rather lax of us and very remiss. It is hardly surprising when not enough consideration is paid to instrumentation in general.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Ian Massi
Ian Massi
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2873 Visits: 2197
It takes a little more time, but changing the exception handling process for a job from "wait for users to notify the right person" to "have SQL Server notify the right person" is definitely worthwhile.

I have checks for jobs that haven't run or haven't finished in a reasonable period of time but we can always use more. It's the irregular processes that run once a month that are hard to pin down.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)

Group: General Forum Members
Points: 232471 Visits: 46360
That's one of the points in my DB corruption presentation. Don't assume everything's OK. Don't assume that the backups are succeeding just because you're not getting backup failure messages.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


dwilliscp
dwilliscp
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2215 Visits: 784
Thanks to SQL Sentry we have built on to our job step -- alert-- and can now check for jobs that run too long. But I do see one more hole... jobs calling code that is not well built, and it completes with out error, but does not do what you expected... I have had this come up from time to time.. the latest issue was bad data flowing into the database and was not picked up until the weekly maint schedule found that the data did not match the data type. One other time we had a trigger that got turned off.. and not turned back on...

David
GoofyGuy
GoofyGuy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1207 Visits: 971
"A job that runs long or doesn't run at all can sting just as bad as one that fails."

What's the difference?

There is no difference.
Miles Neale
Miles Neale
SSCarpal Tunnel
SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

Group: General Forum Members
Points: 4290 Visits: 1695
Developers have in the past cursed bean counters for various reasons. However there are reasons for counting and tracking. Maybe we need to regularly check and see if we have the appropriate beans.

Not all gray hairs are Dinosaurs!
Steve Jones
Steve Jones
SSC Guru
SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)SSC Guru (150K reputation)

Group: Administrators
Points: 150458 Visits: 19454
GoofyGuy (7/31/2014)
"A job that runs long or doesn't run at all can sting just as bad as one that fails."

What's the difference?

There is no difference.


Sure there is. A long running job might be stuck, but it's done some work. If you clear the issue, it may run quicker. Depending on the job, ETL or some check, it might not affect your day to day operations.

One that doesn't run is bad because you might not realize the event hasn't occurred. If there is no issue, like a corruption check, then it might not affect you, but certainly it could in the future. A failure of the same job would be indicative of a problem, at least it's likely.

These all can cause problems, but there certainly is a difference in many cases. Not all, but many.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
GoofyGuy
GoofyGuy
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1207 Visits: 971
Steve Jones - SSC Editor (7/31/2014)
GoofyGuy (7/31/2014)
"A job that runs long or doesn't run at all can sting just as bad as one that fails."

What's the difference?

There is no difference.


Sure there is. A long running job might be stuck, but it's done some work. If you clear the issue, it may run quicker. Depending on the job, ETL or some check, it might not affect your day to day operations.

One that doesn't run is bad because you might not realize the event hasn't occurred. If there is no issue, like a corruption check, then it might not affect you, but certainly it could in the future. A failure of the same job would be indicative of a problem, at least it's likely.

These all can cause problems, but there certainly is a difference in many cases. Not all, but many.


All three cases represent failure to design and test properly. There is no difference, in my mind, from that perspective.
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)

Group: General Forum Members
Points: 68499 Visits: 18570
Miles Neale (7/31/2014)
Developers have in the past cursed bean counters for various reasons. However there are reasons for counting and tracking. Maybe we need to regularly check and see if we have the appropriate beans.


Cool beans.

If the bean counter is our check and balance, maybe that is an indicator we haven't been doing enough testing and verification on our part.:-D



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search