Create a new trace and choose the following events:
Choose the minimal amount of columns (don't forget to add the DatabaseID):
Note: The data columns shown above, make up the minimum list of necessary columns.
Choose the filters, for example:
Run the trace and script it:
Requires Free Membership to View
Targeting SQL Profiler to determine performance problems
Home: Introduction
Step 1: Tracing statements in SQL Server 2000
Step 2: Tracing statements in SQL Server 2005
Step 3: How to use SQL Trace definition
Step 4: Script example for SQL Trace
Step 5: SQL Trace results in SQL Profiler
ABOUT THE AUTHOR: Michelle Gutzait works as a senior databases consultant for ITERGY International Inc., an IT consulting firm specializing in the design, implementation, security and support of Microsoft products in the enterprise. Gutzait has been involved in IT for 20 years as a developer, business analyst and database consultant. For the last 10 years, she has worked exclusively with SQL Server. Her skills include database design, performance tuning, security, high availability, disaster recovery, very large databases, replication, T-SQL coding, DTS packages, administrative and infrastructure tools development, reporting services and more.
Copyright 2007 TechTargetMore on SearchSQLServer.com
- Step-by-Step Guide: How to interpret performance metrics in SQL Server 2005
- Using SQL Server Profiler with Analysis Services
- FAQ: DTS packages in SQL Server
This was first published in March 2007
There are Comments. Add yours.