August 31, 2005 at 8:26 am
found two articles. the first is the MS article I found. THe problem described is not the same problem. but the behavior is the same. The second is an atricle about deadlocks and the author states that you must start or restart the sql server.
I did a lot of testing on this ad the final solution was to restart the SQL Server. I think I reset up the Alert and restated the SQL Server.
http://support.microsoft.com/kb/q239753/
http://www.databasejournal.com/features/mssql/article.php/1498781
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
August 31, 2005 at 8:50 am
This is similar to this post
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=215490
Is this a secret double life?
August 31, 2005 at 8:57 am
don't need trace flag 3605, just need 1204
Try this to set the alert up:
EXEC dbo.sp_add_alert 'Error 1205 - Deadlock detected', 1205, 0, 1, 60, NULL, 5
EXEC dbo.sp_add_notification 'Error 1205 - Deadlock detected', 'whoever', 5
This works for me...
August 31, 2005 at 12:37 pm
Thanks so much guys!
The restart definitely resolved the problem. A restart is usually not an option in my shop unless to resolve a problem even with dev/test servers =(.
April 9, 2014 at 3:09 pm
confirm these, hope this will help
1. DBCC TRACESTATUS
2. Go to sql agent properties\ Alert System and Enable mail profile
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply