Step 5: Transaction-level performance

Learn how to use SQL Profiler and certain commands to capture detailed level information about individual transactions in SQL Server 2000.

The primary tool to capture detailed level information about individual transactions is SQL Profiler. Profiler has can be configured to capture all of the transactions on a server or only a subset based on filtering by application name, host, etc. The information captured by Profiler can be stored in a SQL Server table or a flat file for future reference. This image shows a snippet of Profiler's results.


SQL Profiler

Process-related information can also be captured by the following commands:



Hunt down SQL Server performance problems

 Home: Introduction
 Step 1: CPU usage
 Step 2: Disk IO queuing
 Step 3: Memory consumption
 Step 4: Network bandwidth
 Step 5: Transaction-level performance

ABOUT THE AUTHOR:   
Jeremy Kadlec
Jeremy Kadlec is the Principal Database Engineer at Edgewood Solutions, a technology services company delivering professional services and product solutions for Microsoft SQL Server. He has authored numerous articles and delivers frequent presentations at regional SQL Server Users Groups and nationally at SQL PASS. Jeremy is also the SearchSQLServer.com Performance Tuning expert. Ask him a question here.
Copyright 2005 TechTarget
This was first published in December 2005

Dig deeper on Microsoft SQL Server Performance Monitoring and Tuning

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

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

Your password has been sent to:

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close