• K. Brian Kelley (1/23/2009)


    MarkusB (1/23/2009)


    In SQL 2005 SP2 or higher you can also create a Login trigger to log the logon event into a table.

    You can, but if something were to happen to the table, no one logs in. Been there, heard the screams, hence the reason I recommended the trace. Server side trace would be lightweight, you could really restrict down the columns, and initially it'll write to a file, but you can import that file into a trace table and do your queries that way.

    Maybe I was just lucky, but so far my implementations of Login triggers worked fine. But I totally understand your point. I think it's also a choice between 100% auditing vs. availability of the database..

    [font="Verdana"]Markus Bohse[/font]