September 25, 2009 at 2:53 pm
Our general alerting setup for sql server 2005 is to set up Severity level alerts for levels 11 - 25. Generally this works pretty well. However one new application system is generating numerous errors of a specific type that are included in the level 20 category.
The vendor has told us to ignore those ("The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online".)..for the moment things are working ok.
Question is what is the best approach to keep getting other Severity 20 errors but not this particular one? Is there a better approach to defining the alert that would work for us?
Thanks
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy