Home > IT Answers > SQL Server > Using SQL Profiler to identify the cause of d...
SQL Server Ask the Experts
2440 pts.
0
Q:
Using SQL Profiler to identify the cause of data loss
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?
ASKED: Sep 30 2008  5:42 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Mrdenny
47070 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
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.
Last Answered: Sep 30 2008  7:28 PM GMT by Mrdenny   47070 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



0