Re: Logon triggers
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 19 Aug 2008 14:37:31 -0700
Hugo (Hugo@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I was 'afraid' that was gone be the answer. The howto use Event
Notifications is four times as long as the howto on Logon Triggers.
I understand Event Notifications is much more powerfull and can do a lot
more. Some features I will be looking at for use in the future.
It usually not a good idea to choose a feature from the length of the
tutorial.
It all depends on what you want to achieve. If you want to prevent logins
for some reason, for instance during certain hours, logon triggers is the
way to go. Same if you want fire-proof auditing, and you cannot permit a
login happening without being logged.
On the other hand, if the login action is only nice-to-have, and should
never prevent login from happening, event notifications is the way to go.
However, it's not that if you mess up the login trigger that no one can
connect at all. You can still connect on the DAC (Dedicated Administrator
Connection) to drop the trigger. Either with SQLCMD -A or specify ADMIN:
before the server in SSMS. But keep in mind that the DAC is one single
connection, and by default you can only connect locally on the DAC.
--
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
- References:
- Logon triggers
- From: Hugo
- Re: Logon triggers
- From: Erland Sommarskog
- Re: Logon triggers
- From: Hugo
- Logon triggers
- Prev by Date: Integrate AzMan with SQL Database?
- Next by Date: Re: Integrate AzMan with SQL Database?
- Previous by thread: Re: Logon triggers
- Next by thread: Re: Logon triggers
- Index(es):
Relevant Pages
|