<?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: De-Normalizing your data</title>
	<atom:link href="http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Not Statistically Significant</description>
	<lastBuildDate>Fri, 16 Dec 2011 16:12:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: DavidAiken</title>
		<link>http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/comment-page-1/#comment-819</link>
		<dc:creator>DavidAiken</dc:creator>
		<pubDate>Thu, 15 Apr 2010 17:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/#comment-819</guid>
		<description>Agree, that the cost needs to be taken into account now. But also for the cloud you really need to think about scaling out.

Do keep in mind there are complexities scaling out on SQL Azure. If you think about putting the same app into SQL Azure, it&#039;s unlikely you are going to want it in a single database, maybe for size, but almost certainly for throughput. Keep in mind that you are in a shared environment, and NOT running on a 48 core box with 15,000 rpm drives and 1/2 GB of RAM. - perhaps I need a post on this :)

Disagree that we are working around *missing* functionality.</description>
		<content:encoded><![CDATA[<p>Agree, that the cost needs to be taken into account now. But also for the cloud you really need to think about scaling out.</p>
<p>Do keep in mind there are complexities scaling out on SQL Azure. If you think about putting the same app into SQL Azure, it&#8217;s unlikely you are going to want it in a single database, maybe for size, but almost certainly for throughput. Keep in mind that you are in a shared environment, and NOT running on a 48 core box with 15,000 rpm drives and 1/2 GB of RAM. &#8211; perhaps I need a post on this <img src='http://www.davidaiken.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Disagree that we are working around *missing* functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: perpetualKid</title>
		<link>http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/comment-page-1/#comment-818</link>
		<dc:creator>perpetualKid</dc:creator>
		<pubDate>Thu, 15 Apr 2010 12:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidaiken.com/2010/04/13/de-normalizing-your-data/#comment-818</guid>
		<description>sounds all nice in theory and looks like an solid approach, but cloud patterns may also consider the economics based on the underlyings platform pricing. Viewing an item is a single storage transaction - applying your pattern just to view topmost items, and to workaround some *missing* functionality in table storage, implies 5 more storage transaction thus increasing costs to be six times as much and making SQL (Azure) again more reasonable :(</description>
		<content:encoded><![CDATA[<p>sounds all nice in theory and looks like an solid approach, but cloud patterns may also consider the economics based on the underlyings platform pricing. Viewing an item is a single storage transaction &#8211; applying your pattern just to view topmost items, and to workaround some *missing* functionality in table storage, implies 5 more storage transaction thus increasing costs to be six times as much and making SQL (Azure) again more reasonable <img src='http://www.davidaiken.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

