MSSQLTips

http://www.mssqltips.com/tip.asp?tip=1631

Your article describes exactly the issue I ran into and how i undid the issue using the DAC.

 My new solution uses event notifications, because it is just a logging application that should not block anything in real time.

I posted my little but drastic mishap at SQLserver central to be published in the near future. 

Hi,

I tried the tip and did end up with the Bad login.  However, when I connect DAC as sa it states I do not have permission to delete the trigger.   Please help if you can.

Thank you.

TG

Can you post the exact error message you receive when trying to delete the trigger?

It is strange sa cannot drop that trigger, however maybe just disable it to bypass your original problem.

and search for a solution if things are back running as normal.

Hi,

Thanks for your response.

Msg 3701, Level 11, State 5, Server CISDEVMST01,  Line 1
Cannot drop the trigger 'Trigger_ServerLogon', because it does not exist or you
do not have permission.

TG

I got it!

I had forgotten to put the "on ALL Server" at the end of my drop statement.

Thanks so much everyone.

TG