<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Weaning yourself off of SQL Profiler (Part 1)	</title>
	<atom:link href="https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Jul 2026 23:04:21 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>
		By: Jason Brimhall		</title>
		<link>https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/#comment-60</link>

		<dc:creator><![CDATA[Jason Brimhall]]></dc:creator>
		<pubDate>Mon, 04 Apr 2016 19:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2336#comment-60</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/#comment-59&quot;&gt;rob&lt;/a&gt;.

I am going to be blunt here. I approved this comment only to hopefully clarify this comment if it is a legitimate comment. As currently composed it makes absolutely no sense. The article is discussing converting server side traces to extended events sessions. This article does not discuss either of the two talking points you have raised.

So how can you disagree with this article based on the two talking points you have proposed?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/#comment-59">rob</a>.</p>
<p>I am going to be blunt here. I approved this comment only to hopefully clarify this comment if it is a legitimate comment. As currently composed it makes absolutely no sense. The article is discussing converting server side traces to extended events sessions. This article does not discuss either of the two talking points you have raised.</p>
<p>So how can you disagree with this article based on the two talking points you have proposed?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: rob		</title>
		<link>https://sqlsolutionsgroup.com/wean-off-sql-profiler-part-1/#comment-59</link>

		<dc:creator><![CDATA[rob]]></dc:creator>
		<pubDate>Mon, 04 Apr 2016 14:16:27 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2336#comment-59</guid>

					<description><![CDATA[Hi,

Interesting article, but You are making two assumptions that I find difficult to accept:  1) that you are the only thing that is operating on the database (most of the time, it is other application&#039;s code that is causing the problem and it is the responsibility of my code to be able to dodge the problems that it creates, and 2) that the error itself is the problem - the error is the snowball at the bottom of the hill.  The problem that needs to be fixed was 3,000 SQL Statements before the error occurred.  It is required that you look at all of them to be able to fix the error, not just handle the error.  Handling the error is putting a bandage on the cancer.]]></description>
			<content:encoded><![CDATA[<p>Hi,</p>
<p>Interesting article, but You are making two assumptions that I find difficult to accept:  1) that you are the only thing that is operating on the database (most of the time, it is other application&#8217;s code that is causing the problem and it is the responsibility of my code to be able to dodge the problems that it creates, and 2) that the error itself is the problem &#8211; the error is the snowball at the bottom of the hill.  The problem that needs to be fixed was 3,000 SQL Statements before the error occurred.  It is required that you look at all of them to be able to fix the error, not just handle the error.  Handling the error is putting a bandage on the cancer.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
