June 25, 2004 at 2:23 am
i am using profiler to trace DMLs on my database.
i've set event classes RPC:COMPLETED and SQL:BatchCompleted.
When i insert data thru asp code using ADDNEW command; the profiler doesn't trace the Insert command. However the values get inserted into the database.
How can i square this?
What's the best way to log only DMLs within a database using profiler to remove overhead of tracing Select statements.
Howdy!
June 25, 2004 at 6:56 am
Either use Triggers to audit (only selects won't work) or check you settings for the Trace.
1) Is it pointed at the right server.
2) Are there any filters
3) Make sure profiler is actively running (I did this once so I include).
4) Add a few other TSQL trace items for testing.
June 25, 2004 at 10:15 am
Hi, thanx for ur reply.
I need to trace DML only when i run SNAPSHOT on production system and move my application to a backup database and then insert the logged entries back after SNAPSHOT. Profiler would rather be a good choice than triggers i guess. If there's a better idea, i would be pleased to know.
As i mentioned, i could trace all DML through VB and ASP. Only ADDNEW command doesn't get traced.
I would try a few other TSQL as u suggested.
Howdy!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply