Hi Jordon,

Your solution is what I planned to do as well (unless there was a configuration that allowed Alert definitions at a database level).

So, the Event Alert Definition for Errors 32040, 32042, 32043 and 32044 must not be created for individual databases.

I suspect that the Alert Definition has been built to be flexible (e.g. some Errors are caught by SQL Server Event Alerts at a database level).

I'll post on Microsoft Connect, ServerFault.com as well as here a request to each community to find out if anyone has compiled a list of which Errors are and are not caught by SQL Server Event Alerts at a database level.

Thank you very much for responding to this so promptly. Good luck on completing your workload!

David