Adrian Hills • 2/17/2010

Using the SP:StmtCompleted SQL Profiler trace event class

Read Original

This technical article addresses a common SQL Server performance tuning question: how to pinpoint which specific statements inside a stored procedure are consuming the most time. It critiques clunky manual timing methods and recommends using the often-overlooked SP:StmtCompleted event class in SQL Profiler. This approach provides a detailed trace of each statement's execution, offering a cleaner alternative to modifying code for auditing.

0 comments
#profiler #performance tuning #SQL Server
Using the SP:StmtCompleted SQL Profiler trace event class

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Webinar Series – SQL Server Indexing
Koen Verbeeck • 1 votes
2
Risks and Limitations of AI in the Life Sciences
Jeremy Howard • 1 votes
3
1M context is now generally available for Opus 4.6 and Sonnet 4.6
Simon Willison • 1 votes
4
AI is my CMS
Chris Coyier • 1 votes
5
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
6
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes