Agent Alerts Management Pack updated

re: Agent Alerts Management Pack updated

Dirk Hondong — Mon, 26 Sep 2011 12:50:03 GMT

Hello Tibor,

first of all: thank you for sharing the script. It helped me a lot to set up SQL Agent Alerting in the past.

I just noticed that you´ve updated the script.

There´s one little typo in line 98 (double P at message_id int PRIMARY KEY ...)

Regards

Dirk

re: Agent Alerts Management Pack updated

TiborKaraszi — Mon, 26 Sep 2011 13:10:22 GMT

Thanks Dirk! The tool I use make it HTML (with colors and stuff) sometimes add this extra P, for longer scripts. I've fixed it, thanks for catching it! :-)

re: Agent Alerts Management Pack updated

Rob Pellicaan — Tue, 25 Oct 2011 13:00:35 GMT

Hi Tibor,

2 parts of your article are a bit confusing

1) You say "...We used to be able to enter such "Non Alertable Errors" in the registry key NonAlertableErrors.... This functionality seems to have been removed, I'm afraid."

and later

"I wish we could block out some, but NonAlertableError doesn't seem to work anymore..."

I believe your blogged about the new solution to this issue: http://sqlblog.com/blogs/tibor_karaszi/archive/2009/05/14/sp-altermessage-is-back-in-business.aspx.

2) In your article it is not clearly stated that, although your specify alerts on severity 16, 17 and 18, not all messages of that severity are logged and therefore alerted. Is it an explicit choice on your behalf not to enable alerting on ALL messages of severity 17 and 18? (as MS recommends in http://msdn.microsoft.com/en-us/library/ms164086.aspx)

re: Agent Alerts Management Pack updated

TiborKaraszi — Tue, 25 Oct 2011 18:19:28 GMT

Rob,

Consiguring whether an error is written to eventlog is one thing - this is what you can control using sp_altermessage. NonAlertableErrors is a different thing - it allow you to block *agent* from triggering on an alert already written to eventlog. Very handy if you capture all alerts with a specific severity level, but want Agent to *not* trigger from some selected in that severity level (but still have them in the EventLog).

2) You mean reconfigure all alerts with 17 and 18 to go to eventlog? I never thought of it from that perspective. Instead I went through sys.messages, error by error and gave each error message some thoughts (notonly 17 and 18)...

re: Agent Alerts Management Pack updated

Rob Pellicaan — Wed, 26 Oct 2011 11:12:12 GMT

Hi Tibor,

I see what you mean now; They are indeed two different things. It is indeed a pity that there is no distinction to be made between raising alerts and writing to the event log. I can even imagine situations where you want certain alerts to be raised without having to write them to the eventlog.

Thank you for sharing the script!

re: Agent Alerts Management Pack updated

Stefan K. — Mon, 02 Jul 2012 07:39:37 GMT

Hi Tibor,

please add Error 833.

SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database [%ls] (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x

re: Agent Alerts Management Pack updated

TiborKaraszi — Tue, 03 Jul 2012 11:40:24 GMT

Done, 833 added. Thanks Stefan!