{"id":949,"date":"2009-02-23T10:34:00","date_gmt":"2009-02-23T10:34:00","guid":{"rendered":"\/blogs\/paul\/post\/Easy-monitoring-of-high-severity-errors-create-Agent-alerts.aspx"},"modified":"2017-04-13T11:41:55","modified_gmt":"2017-04-13T18:41:55","slug":"easy-monitoring-of-high-severity-errors-create-agent-alerts","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/paul\/easy-monitoring-of-high-severity-errors-create-agent-alerts\/","title":{"rendered":"Easy monitoring of high-severity errors: create Agent alerts"},"content":{"rendered":"

<\/p>\n

\nIn my previous post<\/a> today I talked about error 825 and how you should have an Agent alert set up to catch it when it happens. There are two ways you can set up Agent alerts – using SSMS or using the stored-proc sp_add_alert<\/font>. In a post from April 2008 I showed how to create an Operator and alerts using the SSMS wizards (see that post here<\/a>). To use the SP to create the alert for message 825, the code would be as follows:\n<\/p>\n

<\/font><\/p>\n

\n\tUSE<\/font> msdb;<\/font>
\n\tGO <\/p>\n

\n\tEXEC<\/font> msdb.<\/font>dbo.<\/font>sp_add_alert<\/font> @name =<\/font> N'825 – Read-Retry Required'<\/font>,<\/font>
\n\t    @message_id =<\/font> 825,<\/font>
\n\t    @severity =<\/font> 0,<\/font>
\n\t    @enabled =<\/font> 1,<\/font>
\n\t    @delay_between_responses =<\/font> 0,<\/font>
\n\t    @include_event_description_in =<\/font> 1;<\/font>
\n\tGO\n\t<\/p>\n<\/blockquote>\n

<\/font><\/p>\n

\nNote the @include_event_description<\/font> parameter. This is a tinyint<\/font> that says which of the notification mechanisms should include the description. The list of possibilities is:\n<\/p>\n