How to run a SQL profiler trace for SQL Server

1. Start SQL Profiler from Start - Microsoft SQL Server - Performance Tools - SQL Server Profiler.

2. Go to File - New Trace to start a new trace.

3. Ensure that the Server Type is Database Engine and the authentication type is Windows Authentication and click Connect.
 

4. From the drop down menu under Use the template, choose Blank  (it's the top choice so scroll up)

5. Enter a trace name, and click Save to file and enter a file name on a drive with sufficient disk space.

 

6. Set the Maximum File Size to 250 and select the option: Enable file rollover.

 

7. Click on the Events Selection tab 

 

8. Deselect all existing events in the left column, and click Show all events box to show all events.

9. Expand Stored Procedures and click to select the following checkboxes:

  Figure 2
 

  Note: Please select SP:StmtStarting and SP:StmtCompleted events, if the issue occurs while executing a statement within a Stored procedure.

10. Click Show all columns box to show all columns.

11. To filter on a specific databaseID or database name, click on the 'Column Filters' and then in Edit Filter dialogue box, click on column header DatabaseID or DatabaseName and enter the DBID/Name and click OK. (Figure 3)

  Figure 3
 

12. Click the Run button to start tracing, and then reproduce the problem in order to capture information in the trace log.

13. After the problem is reproduced successfully, click on the Stop Selected Trace button.

14. [OPTIONAL] Go to File - Save As - Trace Template to save the setting as template in case the trace needs to be run again.

15. Compress the output trace log specified in Step 4, and send to Veritas Support.

For more information about SQL Profiler, please refer to the following Microsoft article: