Problem solve
Get help with specific problems with your technologies, process and projects.
Tracing statements in SQL Server 2000
Use SQL Profiler in your production environment to target poorly performing T-SQL commands in SQL Server 2000 and SQL 2005. Microsoft database expert Michelle Gutzait guides you through SQL Trace, from how to use trace definition through incorporating SSIS/DTS packages into the process. Locate problematic T-SQL commands and send the reports to your SQL Server development team.
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.
Download: 60-Page Expert RDBMS Guide
Trends come and go, but your DB strategy shouldn’t be a flavor of the month. Learn why you shouldn’t get distracted by new DB technology, how Facebook is using a RDBMS to do the data slicing and dicing they can’t in Hadoop, and more.
Choose the filters, for example:
Run the trace and script it:
Targeting SQL Profiler to determine performance problems
Home: Introduction
| 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 TechTarget |
More on SearchSQLServer.com
This was last published in March 2007
Start the conversation
0 comments