Posted by Erland Sommarskog on 07/24/05 18:20

akej via SQLMonster.com (forum@SQLMonster.com) writes:
>>2) Use Profiler.
>
>
> can u plz explain me how to acomplish it using Profiler???
>
> i'm newb and use for profiler only for checking for sp recompilation and
> so on.

You would have to catch the SP:StmtCompleted and SQL:StmtCompleted events,
and probably add some filters on it as well. You should trace to a file
or a table rather than to the GUI, so you can load the trace into a table
and analyse it later.

If it sounds messy, it is because it is - messy.

Personally, if I were to implement an auditiing scheme I would into some
3rd party product like Lumigent's Entegra (which works on the transaction
log) or Red Matrix's SQL Audit (which works ny triggers). I would not call
running a constant Profiler trace an adequate auditing solution, because
the information you get is too unstructures. Possibly one could write a
tool that reads the Profiler output and build some useful information
from that. But that is not a minor undertaking.

Profiler could be sufficient if you only need to answer the question
"who did last change X" may be every second month or so, and you are
prepared to spend an hour each time to dig up the answer.


--
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

[Back to original message]