 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / DB Engine / SQL Server / August 2008ALerts not working
I'm running SQL SErver 2005. I've created an SQL Alert for events of severity 15 (syntax errors). I created an Operator with my name. I added my email and my net send address to the operator. I assigned that operator to the Alert. I then went into management studio and issued the following command: select * form mytable Notice the Intentional misspelling of FROM. This issued an error of severity 15, but I got no alert, and the alert count in the SSMS UI hasn't incremented. I've confirmed that SQL SErver Agent is running. There is nothing useful in the event viewer for the database server, and SQL Server agent runs under the same domain user that sql server runs under. I've also confirmed that the event log is running, and nothing useful appears in the Error Logs in SSMS. What else should I check? Thanks, JRF Most messages *do not* end up in eventlog/errorlog. Those cannot be caught by an alert (since Eventlog is what Agent polls). This is the way it is, quite simply. In 2000 and earlier you could configure whether an error should go to eventlog (sp_altermessage) but that possibility isn't available as of 2005.  SignatureTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi > I'm running SQL SErver 2005. I've created an SQL Alert for events of severity 15 (syntax > errors). [quoted text clipped - 20 lines] > > JRF what then is the purpose behind setting alerts for severity 15 if they dont get logged? Is it effectively broken and therefore should probably be removed from the dropdown list? Or can it be activated through setting a trace flag? > Most messages *do not* end up in eventlog/errorlog. Those cannot be caught > by an alert (since Eventlog is what Agent polls). This is the way it is, [quoted text clipped - 29 lines] >> >> JRF > what then is the purpose behind setting alerts for severity 15 if they dont get logged? In general, severity doesn't say much about the ... severity of the error/exception. So there are messages with a low severity which are logged, and vice versa. As for level 15, it happens that this level has no messages that are logged. Consider submitting at connect if you want this level to not to be shown in the drop-down. Here's a query to show all errors which are logged (20 and higher are logged regardless of is_event_logged column): SELECT * FROM sys.messages WHERE (is_event_logged = 1 OR severity > 20) AND language_id = 1033 ORDER BY severity, message_id SignatureTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi > what then is the purpose behind setting alerts for severity 15 if they dont get logged? > [quoted text clipped - 31 lines] >>> >>> JRF |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.