Posted by Erland Sommarskog on 07/22/05 00:21

byrocat (bdealhoy@sympatico.ca) writes:
> On the other database types, there is an audit capability in that you
> record such items as
> failed login attempts
> attemtped access to tables user is not authroized to
> changes to databse schema
> changes to permissions
> changes to logins (add, delete, lock, unlock, passwrod reset)

In SQL 2000 a Profiler trace is the only option, save for failed logins
which can be tracked by other means.

In SQL 2005 you can set up server and database triggers to audit the
last three events. SQL 2005 is currently in beta.

Attempt to access tables for which user does not have permission is
not something you can track well even in SQL 2005. In fact if a user
says "SELECT * FROM tbl_I_may_not_see" he gets as the same error message
as if it did not exist at all.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: ADODB connection with SQL2000SP3
• Prev in forum: Re: WHAT DO I USE TO MAKE A TODAY DATE QUERY?
• Thread view: Re: Auditing user and security related activities in SQLServer

[Reply to this message]