<?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: Reproduce, then Repeat</title>
	<atom:link href="http://thomaslarock.com/2009/09/reproduce-then-repeat/feed/" rel="self" type="application/rss+xml" />
	<link>http://thomaslarock.com/2009/09/reproduce-then-repeat/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 16:15:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Log Buffer #161: a Carnival of the Vanities for DBAs &#171; PlanetMysql.ru &#8211; ?????????? ? ???? MySQL</title>
		<link>http://thomaslarock.com/2009/09/reproduce-then-repeat/comment-page-1/#comment-968</link>
		<dc:creator>Log Buffer #161: a Carnival of the Vanities for DBAs &#171; PlanetMysql.ru &#8211; ?????????? ? ???? MySQL</dc:creator>
		<pubDate>Fri, 11 Sep 2009 19:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=2504#comment-968</guid>
		<description>[...] I have two pet peeves when it comes to the IT Industry practices: 1. Lack of attention to details; and 2. wasted resources. In Can you be too Thorough? Jason Massie talks about being thorough (a way to have attention to detail), and knowing when to stop in a project (a way to avoid waste of resources). Thomas LaRock offers another twist on the subject with Reproduce, then Repeat. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have two pet peeves when it comes to the IT Industry practices: 1. Lack of attention to details; and 2. wasted resources. In Can you be too Thorough? Jason Massie talks about being thorough (a way to have attention to detail), and knowing when to stop in a project (a way to avoid waste of resources). Thomas LaRock offers another twist on the subject with Reproduce, then Repeat. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Log Buffer #161: a Carnival of the Vanities for DBAs &#124; Pythian Group Blog</title>
		<link>http://thomaslarock.com/2009/09/reproduce-then-repeat/comment-page-1/#comment-967</link>
		<dc:creator>Log Buffer #161: a Carnival of the Vanities for DBAs &#124; Pythian Group Blog</dc:creator>
		<pubDate>Fri, 11 Sep 2009 17:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=2504#comment-967</guid>
		<description>[...] I have 2 pet peeves when it comes to the IT Industry practices: 1. Lack of attention to details and 2. waste resources. In Can you be too Thorough? Jason Massie talks about being thorough (a way to have attention to detail) and knowing when to stop in a project (a way to avoid waste of resources). Thomas LaRock offers another twist on the subject with Reproduce, then Repeat. [...]</description>
		<content:encoded><![CDATA[<p>[...] I have 2 pet peeves when it comes to the IT Industry practices: 1. Lack of attention to details and 2. waste resources. In Can you be too Thorough? Jason Massie talks about being thorough (a way to have attention to detail) and knowing when to stop in a project (a way to avoid waste of resources). Thomas LaRock offers another twist on the subject with Reproduce, then Repeat. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Ozar</title>
		<link>http://thomaslarock.com/2009/09/reproduce-then-repeat/comment-page-1/#comment-966</link>
		<dc:creator>Brent Ozar</dc:creator>
		<pubDate>Thu, 10 Sep 2009 13:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=2504#comment-966</guid>
		<description>Nice post.  The other thing that&#039;s deceiving about duration is that users with slower computers or slower network connections can skew duration artificially high.  If you&#039;ve got an application whose end users are all on slow VPN connections and they&#039;re pulling down big recordsets with, oh, I dunno, Microsoft Access (true story) then the duration will seem high.  The queries can&#039;t be optimized any faster, though, because SQL Server is waiting to send the results over the wire.  Another good reason to check out wait stats to see the real problem.</description>
		<content:encoded><![CDATA[<p>Nice post.  The other thing that&#8217;s deceiving about duration is that users with slower computers or slower network connections can skew duration artificially high.  If you&#8217;ve got an application whose end users are all on slow VPN connections and they&#8217;re pulling down big recordsets with, oh, I dunno, Microsoft Access (true story) then the duration will seem high.  The queries can&#8217;t be optimized any faster, though, because SQL Server is waiting to send the results over the wire.  Another good reason to check out wait stats to see the real problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: basic
Database Caching 7/12 queries in 0.782 seconds using disk: basic
Object Caching 447/448 objects using disk: basic

Served from: thomaslarock.com @ 2012-02-08 12:08:21 -->
