<?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: So You Want to Scale Out?</title>
	<atom:link href="http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/</link>
	<description>SQL, Performance, Cloud, Bad Humor</description>
	<lastBuildDate>Sun, 15 Nov 2009 13:34:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Something for the Weekend 17/07/09 &#124; John Sansom - SQL Server DBA in the UK</title>
		<link>http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/comment-page-1/#comment-48</link>
		<dc:creator>Something for the Weekend 17/07/09 &#124; John Sansom - SQL Server DBA in the UK</dc:creator>
		<pubDate>Fri, 17 Jul 2009 10:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/#comment-48</guid>
		<description>[...] So You Want to Scale Out? &#8211; Not to be confused with an expanding waistline, Jason Massie talks us through three of the SQL Server scale out implementations he has worked on. [...]</description>
		<content:encoded><![CDATA[<p>[...] So You Want to Scale Out? &#8211; Not to be confused with an expanding waistline, Jason Massie talks us through three of the SQL Server scale out implementations he has worked on. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lara Rubbelke</title>
		<link>http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/comment-page-1/#comment-45</link>
		<dc:creator>Lara Rubbelke</dc:creator>
		<pubDate>Tue, 14 Jul 2009 06:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/#comment-45</guid>
		<description>Good summary.  I would add that one should never use merge rep in continuous mode. Bad things will ensue.</description>
		<content:encoded><![CDATA[<p>Good summary.  I would add that one should never use merge rep in continuous mode. Bad things will ensue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Lathrope</title>
		<link>http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/comment-page-1/#comment-44</link>
		<dc:creator>Chuck Lathrope</dc:creator>
		<pubDate>Mon, 13 Jul 2009 22:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/#comment-44</guid>
		<description>We use transactional one-way replication to offload work to multiple groups of servers that sit behind an F5 BigIP load balancer and have great success. We have one group dedicated to 3rd party communications, one for authentication and reporting offloading, and one for DNS lookup data. Each group has 3-5 servers. Works well and is better than trying to horizontally partition for us as it would just be too hard.</description>
		<content:encoded><![CDATA[<p>We use transactional one-way replication to offload work to multiple groups of servers that sit behind an F5 BigIP load balancer and have great success. We have one group dedicated to 3rd party communications, one for authentication and reporting offloading, and one for DNS lookup data. Each group has 3-5 servers. Works well and is better than trying to horizontally partition for us as it would just be too hard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel McKinney</title>
		<link>http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/comment-page-1/#comment-43</link>
		<dc:creator>Noel McKinney</dc:creator>
		<pubDate>Mon, 13 Jul 2009 18:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://jasonmassie.com/archive/2009/07/so-you-want-to-scale-out/#comment-43</guid>
		<description>It can be difficult to get the budget for hardware that will scale up to the anticipated workload. This is where scale out can work well if you can tie it to revenue. I&#039;ve had projects partitioned by client so that more clients -&gt; more revenue -&gt; justifies adding a server. It&#039;s a pain to manage a bunch of servers, but sometimes this becomes the only realistic solution.</description>
		<content:encoded><![CDATA[<p>It can be difficult to get the budget for hardware that will scale up to the anticipated workload. This is where scale out can work well if you can tie it to revenue. I&#39;ve had projects partitioned by client so that more clients -&gt; more revenue -&gt; justifies adding a server. It&#39;s a pain to manage a bunch of servers, but sometimes this becomes the only realistic solution.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
