@Johan, Very interesting approach! I am considering using it, but I have a question: When the error is raised, which account does it run under? Nevermind! Just realized that the job is run by the alert, so it is run by the account that runs sql agent. Sounds like the disable of the job is a fun way to annoy my production DBAs!