Re: Logon triggers
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 18 Aug 2008 14:34:47 -0700
Hugo (Hugo@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I am searching for the best way to log all logins using sysadmin users.
I want to record the time, username, hostname and application-name.
There are to many users with sysadmin rights and I need some for info
from the system before changing that. I am running SQL 2005 SP2.
I am looking at logon triggers, but I understand that if the trigger
fails (like when my audit table is unavailable) no one (or at least no
sysadmins) will have access to the server. Is this correct? How to
resolve?
I have a hinch that logon triggers may be bypassed when you log over
the DAC, but since all you want to do is auditing, I think event
notifications are a better bet. I cannot really give an example, as I
have not used them myself much.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: Logon triggers
- From: Hugo
- Re: Logon triggers
- From: Uri Dimant
- Re: Logon triggers
- References:
- Logon triggers
- From: Hugo
- Logon triggers
- Prev by Date: Re: Table Permissions
- Next by Date: Re: Locked Out of Local Instance
- Previous by thread: Re: Logon triggers
- Next by thread: Re: Logon triggers
- Index(es):
Relevant Pages
|
