logon logout auditing

Question

logon logout auditing

Viewing 4 posts - 16 through 18 (of 18 total)

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

steve block SSCertifiable Points: 7698 More actions · Answer 1

I haven't worked with Login Triggers but why in the world would you what to allow a user to Login if the original Login failed? There are more than one reason it could fail. If it is a Sql Login, they might have the wrong password. They might not have permissions in the database. They might not even be set up as a user to Sql Server.

In fact, I would look into notifying you instead of the user (assuming that you are the DBA) with the reason for the failure so you can take action.

Steve

Mad-Dog SSCertifiable Points: 6117 More actions · Answer 2

what i meant is if the user successfully made the logon but failed in the trigger because something is wrong with the trigger (the table was delete or no permission to that specific table) if any of those thing happen the user will not be able to logon (error in logon trigger he will get).

how i can avoid it by let the user to logon and alert me on this error?

(if the user mistake in the password the trigger is not fire at all)

THX

steve block SSCertifiable Points: 7698 More actions · Answer 3

Like I said, I haven't worked with Login Triggers, but here is a thread that talks a lot about it. Evidently, if there is a problem with the trigger, it can cause some big problems.

http://www.sqlservercentral.com/Forums/Topic545146-146-1.aspx

Steve

alen teplitsky SSC-Dedicated Points: 30014 More actions · Answer 4

a year or so ago we decided to implement logon triggers. tested in QA first. good thing because we locked out the server for 3 hours or so until i remembered the DAC feature and used it to go in and delete the trigger. QA wasn't happy since they are on a tight schedule