<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>profiler on AdaTheDev Blog</title><link>https://www.adathedev.co.uk/tags/profiler/</link><description>Recent content in profiler on AdaTheDev Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>adathedev@gmail.com (Adrian Hills)</managingEditor><webMaster>adathedev@gmail.com (Adrian Hills)</webMaster><lastBuildDate>Wed, 17 Feb 2010 22:42:00 +0000</lastBuildDate><atom:link href="https://www.adathedev.co.uk/tags/profiler/index.xml" rel="self" type="application/rss+xml"/><item><title>Using the SP:StmtCompleted SQL Profiler trace event class</title><link>https://www.adathedev.co.uk/2010/02/stmtcompleted-sql-profiler-trace-event.html</link><pubDate>Wed, 17 Feb 2010 22:42:00 +0000</pubDate><author>adathedev@gmail.com (Adrian Hills)</author><guid>https://www.adathedev.co.uk/2010/02/stmtcompleted-sql-profiler-trace-event.html</guid><description>One question I&amp;rsquo;ve seen popping up a few times recently, is how to check what individual statement(s) within an SQL Server stored procedure are taking the most time.
The scenario is that there is a stored procedure that consists of a number of SQL statements. The stored procedure has been flagged up as running slower than perhaps it was expected to, but as there are a number of statements/queries within it, it&amp;rsquo;s not immediately clear where the time is being taken.</description></item></channel></rss>