<?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: SQL SERVER - Introduction to Log Viewer</title>
	<atom:link href="http://blog.sqlauthority.com/2008/07/23/sql-server-introduction-to-log-viewer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2008/07/23/sql-server-introduction-to-log-viewer/</link>
	<description>Notes of a SQL Server MVP and Database Administrator</description>
	<pubDate>Wed, 07 Jan 2009 18:55:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ali</title>
		<link>http://blog.sqlauthority.com/2008/07/23/sql-server-introduction-to-log-viewer/#comment-40734</link>
		<dc:creator>ali</dc:creator>
		<pubDate>Thu, 24 Jul 2008 06:43:17 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=728#comment-40734</guid>
		<description>nice, thank</description>
		<content:encoded><![CDATA[<p>nice, thank</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Srinivasan Prasanna</title>
		<link>http://blog.sqlauthority.com/2008/07/23/sql-server-introduction-to-log-viewer/#comment-40702</link>
		<dc:creator>Srinivasan Prasanna</dc:creator>
		<pubDate>Wed, 23 Jul 2008 15:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://sqlauthority.wordpress.com/?p=728#comment-40702</guid>
		<description>Pinal
Thanks for the article on the SQL log. While the logs are useful for many purposes, more often than ever they are very confusing and overwhelming with the number of records. Would it be possible for you to write few articles to decipher the log in a simple fashion approach, that is for some generic scenario's like (CPU usage, culprit transaction etc) what kind of message some one should be looking for. I could very well google this and find out but so far the articles I have seen are little bit overwhelming with ton of information and I have come to love your simple, practical fashion approach.

Thanks much</description>
		<content:encoded><![CDATA[<p>Pinal<br />
Thanks for the article on the SQL log. While the logs are useful for many purposes, more often than ever they are very confusing and overwhelming with the number of records. Would it be possible for you to write few articles to decipher the log in a simple fashion approach, that is for some generic scenario&#8217;s like (CPU usage, culprit transaction etc) what kind of message some one should be looking for. I could very well google this and find out but so far the articles I have seen are little bit overwhelming with ton of information and I have come to love your simple, practical fashion approach.</p>
<p>Thanks much</p>
]]></content:encoded>
	</item>
</channel>
</rss>
