Post reply

Logon Trigger continues to execute, even after being dropped

  • January 28, 2015 at 5:10 pm

    #397941

    Hi,

    I hope someone can help me with this. i created a logon trigger, on a 2008 R2, service pack 2. I have dropped the trigge, but it continues to execute. i recreated it, using different code, but the old code continues to execute. currently, the trigger is dropped, and select * from sys.server_triggers returns no rows. I even did a freeproccache, as a nuclear option, but still no go. the trigger continues to fire.

    Here is the drop i used, which completed successfully.

    DROP TRIGGER [LogonAuditTrigger] ON ALL SERVER ;

    GO

    this is how i created the the trigger. i can post the code, but that isn't the issue. the drop is.

    CREATE TRIGGER LogonAuditTrigger

    ON ALL SERVER WITH EXECUTE AS 'sa'

    FOR LOGON

    AS

    Anybody seen this before, and how do i stop it, short of a restart?

    Thanks,

    Leonard

  • January 30, 2015 at 7:48 am

    #1774354

    I found it my issue. It seems the trigger generated thousands of emails, that ended up in my SQL unsent email table, and SQL was sending those. so even after i had dropped the trigger, there were still emails being sent from the unsent table. once i deleted those, my emails stopped coming. On that note, i am testing, and for each connection, it inserts 19 rows into my test table. I am going to start another post, for this issue.

    Thanks,

    Leonard

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply