<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Guest Posts &#8211; Feodor Georgiev &#8211; The Context of Our Database Environment &#8211; Going Beyond the Internal SQL Server Waits &#8211; Wait Type &#8211; Day 21 of 28</title>
	<atom:link href="http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 17 May 2013 15:26:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #017 &#124; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/#comment-426033</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Weekly Series &#8211; Memory Lane &#8211; #017 &#124; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Sat, 23 Feb 2013 01:31:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=11917#comment-426033</guid>
		<description><![CDATA[[...] Guest Posts – Feodor Georgiev – The Context of Our Database Environment – Going Beyond the Int... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Guest Posts – Feodor Georgiev – The Context of Our Database Environment – Going Beyond the Int&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucky</title>
		<link>http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/#comment-383744</link>
		<dc:creator><![CDATA[Lucky]]></dc:creator>
		<pubDate>Fri, 30 Nov 2012 07:30:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=11917#comment-383744</guid>
		<description><![CDATA[I have used begin transaction in stored procedure that sp used about 1500 To 2000 times in one day for insert the record in 4 tables and fired the some triggers on two tables then updates the 3 to 4 tables records.some time my transaction come in sleeping mode. then i kill the transaction then insert the record.Plz tell the sol.]]></description>
		<content:encoded><![CDATA[<p>I have used begin transaction in stored procedure that sp used about 1500 To 2000 times in one day for insert the record in 4 tables and fired the some triggers on two tables then updates the 3 to 4 tables records.some time my transaction come in sleeping mode. then i kill the transaction then insert the record.Plz tell the sol.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feodor</title>
		<link>http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/#comment-119850</link>
		<dc:creator><![CDATA[Feodor]]></dc:creator>
		<pubDate>Mon, 21 Feb 2011 09:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=11917#comment-119850</guid>
		<description><![CDATA[Marko, please do not give up your blog post. I know you are one of the brightest DBAs in the Nordics and I am sure you have plenty more to say on the subject. 

(Well, if you do not feel like giving your blog post to Pinal, give it to me and I will post it on my blog :) )]]></description>
		<content:encoded><![CDATA[<p>Marko, please do not give up your blog post. I know you are one of the brightest DBAs in the Nordics and I am sure you have plenty more to say on the subject. </p>
<p>(Well, if you do not feel like giving your blog post to Pinal, give it to me and I will post it on my blog :) )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marko Parkkola</title>
		<link>http://blog.sqlauthority.com/2011/02/21/sql-server-the-context-of-our-database-environment-going-beyond-the-internal-sql-server-waits-wait-type-day-21-of-28/#comment-119813</link>
		<dc:creator><![CDATA[Marko Parkkola]]></dc:creator>
		<pubDate>Mon, 21 Feb 2011 07:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=11917#comment-119813</guid>
		<description><![CDATA[Good article! I read half of it and thought that I digest it first before going ahead with the other half.

I&#039;ll just have one thing to add. ASYNC_NETWORK_IO is normal wait state if the process is not running anymore. You need to check cmd column in sys.sysprocesses view. If it says AWAITING COMMAND then everything&#039;s OK. But if it says SELECT the process has ended the query but is still sending data. This tells that you have performance issues with the network or with the receiving end.

In fact, if you run the query SELECT * FROM sys.sysprocesses; you&#039;ll see that there&#039;s always one process in the state ASYNC_NETWORK_IO/SELECT and that&#039;s your own query :)

Pinal, I don&#039;t think I&#039;m going to write the article I was talking about in the email. This Feodor&#039;s post covers everything I was going to write and I really don&#039;t have much to add.

-Marko]]></description>
		<content:encoded><![CDATA[<p>Good article! I read half of it and thought that I digest it first before going ahead with the other half.</p>
<p>I&#8217;ll just have one thing to add. ASYNC_NETWORK_IO is normal wait state if the process is not running anymore. You need to check cmd column in sys.sysprocesses view. If it says AWAITING COMMAND then everything&#8217;s OK. But if it says SELECT the process has ended the query but is still sending data. This tells that you have performance issues with the network or with the receiving end.</p>
<p>In fact, if you run the query SELECT * FROM sys.sysprocesses; you&#8217;ll see that there&#8217;s always one process in the state ASYNC_NETWORK_IO/SELECT and that&#8217;s your own query :)</p>
<p>Pinal, I don&#8217;t think I&#8217;m going to write the article I was talking about in the email. This Feodor&#8217;s post covers everything I was going to write and I really don&#8217;t have much to add.</p>
<p>-Marko</p>
]]></content:encoded>
	</item>
</channel>
</rss>
