tag:blogger.com,1999:blog-7499216.post116351285896462055..comments2011-03-28T05:49:03.163+02:00Comments on Frederik Vandeputte: SQL Server Logon triggers part 2Frederik Vandeputtehttp://www.blogger.com/profile/03145049073278289064noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7499216.post-33430216597713013412011-03-28T05:49:03.163+02:002011-03-28T05:49:03.163+02:00Very interesting entry.
I tried it out--with a few...Very interesting entry.<br />I tried it out--with a few changes--on several servers. I ran into two problems that others may wish to be careful about. Of course these are simple once the cause is identified, but that is not always immediately apparent.<br /><br />1) Be very careful about the code before applying. I had a typo in the INSERT table. When I next needed log in, all accounts failed. The only solution was to login with the DAC and disable to trigger. The command is "DISABLE Trigger ON ALL SERVER;".<br /><br />2) Be sure that each user has sufficient permissions to write to the INSERT table. We had some restricted user accounts that failed login due to this.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7499216.post-87959879355329164422008-02-28T20:18:00.000+01:002008-02-28T20:18:00.000+01:00Is there a way to just trap logons to a particular...Is there a way to just trap logons to a particular database on the server?Anonymousnoreply@blogger.com