Re: SQL Server 2000 Audit for login
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 22:53:44 +0000 (UTC)
Jacand4321 (jacand4321@xxxxxxxxx) writes:
> Thanks Tony for the reply. I'm wondering, if it is going to add any
> significant overhead on the database.
As long as you only catch login events, there is not too much overhead.
However, it's better to use a server-side trace and trace to a file, and
this is leaner on resources. Look up the sp_trace procedures in Books
Online.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- SQL Server 2000 Audit for login
- From: Jacand4321
- Re: SQL Server 2000 Audit for login
- From: Tony Rogerson
- Re: SQL Server 2000 Audit for login
- From: Jacand4321
- SQL Server 2000 Audit for login
- Prev by Date: Re: Views vs Stored Procedures, whats the difference?
- Next by Date: Re: SQL Server does not exist or access denied
- Previous by thread: Re: SQL Server 2000 Audit for login
- Next by thread: MS Access Frontend for remote sql server
- Index(es):
Relevant Pages
|