Identifying performance issues using SQL Server Profiler

By Rob Volk on 26 November 2002 | Tags: Performance Tuning , Profiler & Trace


Narayana Vyas Kondreddi submitted "It is always better to be proactive than reactive, when it comes to identifying and eliminating SQL Server performance issues. In this article, I am going to explain the method I follow, to identify performance issues in my database applications, before those applications go into production environment."

Link: Identifying performance issues using SQL Server Profiler


Related Articles

Testing with Profiler Custom Events and Database Snapshots (22 June 2009)

Introduction to SQL Server 2008 Extended Events (19 May 2009)

Integrating Profiler and PerfMon Log Files (6 February 2008)

Which is Faster: SAN or Directly-Attached Storage? (21 January 2008)

Benchmarking Disk I/O Performance: Size Matters! (30 October 2007)

What I Wish Developers Knew About SQL Server (Presentation) (11 October 2007)

Introduction to Parameterization in SQL Server (7 August 2007)

Using Indexed Computed Columns to Improve Performance (16 January 2007)

Other Recent Forum Posts

Trigger is not allowing the database to populate when enabled. (2d)

Trigger is causing database to not populate (2d)

Consecutive count of holidays if first date of a month is holiday (4d)

Issues With Not Having Permissions To Add New Database (7d)

I need help with checking the sql query (15d)

Setting Min Server Memory (24d)

average duration increasing inline with exec counts (24d)

UOM parameter (30d)

- Advertisement -