Using SQL Profiler to identify the cause of data loss

Tags:
SQL Server
SQL Server database
SQL Server Profiler
We have a SQL database where a table is having information vanish. We plan to use SQL Profiler to identify the cause of this sudden data loss. When using SQL Profiler, what counters should be captured? Also, what trace format should be used?
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Use the Default template. Turn off all the defaults except the SQL:BatchComplete and turn on the SP:StmtCompleted

This will capture all the stored procedures and regular SQL, as well as all the commands within the stored procedures which are being executed. After the data loss has happened again stop the trace and use the find feature of SQL Profiler to look for DELETE commands.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: