Re: Audit stored procedures
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 01:10:17 -0700
Sheela (Sheela@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
There are over 100 stored procedures that access data from a set of
tables in a database. Users use these stored procedures to get different
type of data from the tables. I would like to find out who read data
from the tables without having to run SQL Profiler. Is there a way to do
it?
Rather than using Profiler, use a server-side trace instead. This is a lot
leaner on resources. The simplest way to get started is to set up a trace
in Profiler, and then select Export from the File menu. Be careful to test
the trace when you set it up, because Profiler does not always script the
trace correctly.
If your question was meant to be "how do I audit without any trace at all",
I'm afraid that in SQL 2005 your options are a bit limited. There are some
third-party products like Lumigent's auditing tool, but I guess in runs
a trace somewhere for you.
In SQL 2008 there are new auditing capabilities.
--
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
.
- Prev by Date: Re: Audit stored procedures
- Next by Date: Re: user permissions
- Previous by thread: Re: Audit stored procedures
- Index(es):
Relevant Pages
|
Loading
