<?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 Azure Woes</title>
	<atom:link href="http://thomaslarock.com/2010/04/sql-azure-woes/feed/" rel="self" type="application/rss+xml" />
	<link>http://thomaslarock.com/2010/04/sql-azure-woes/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 18:00:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: SQL Azure Videos &#124; SQLRockstar</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1420</link>
		<dc:creator>SQL Azure Videos &#124; SQLRockstar</dc:creator>
		<pubDate>Thu, 22 Apr 2010 20:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1420</guid>
		<description>[...] I have been railing on SQL Azure lately, I thought I could share with you some of the videos you can watch for free over at MSDN. In case [...]</description>
		<content:encoded><![CDATA[<p>[...] I have been railing on SQL Azure lately, I thought I could share with you some of the videos you can watch for free over at MSDN. In case [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas LaRock</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1419</link>
		<dc:creator>Thomas LaRock</dc:creator>
		<pubDate>Sun, 18 Apr 2010 12:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1419</guid>
		<description>It&#039;s all the same company. If they don&#039;t have good checks for usability or quality control in one area, why should i assume they will be any better in a different area?

imagine if a car company like Toyota suddenly started to put out cars of lesser quality because one area lost focus on quality control and usability...</description>
		<content:encoded><![CDATA[<p>It&#8217;s all the same company. If they don&#8217;t have good checks for usability or quality control in one area, why should i assume they will be any better in a different area?</p>
<p>imagine if a car company like Toyota suddenly started to put out cars of lesser quality because one area lost focus on quality control and usability&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1418</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Sun, 18 Apr 2010 04:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1418</guid>
		<description>The stuff that works is described in SQL Online Books, the regular dev docs that come with every edition of MSSQL.  So I believe the intent is to say &quot;everything you know about MSSQL works except these few things and I&#039;ll give you a link to a detailed description of them there so you know exactly what I&#039;m talking about&quot;

BTW, I&#039;m not commenting from a position of authority (I don&#039;t know the folks who made those decisions and I don&#039;t work there). I was trying to help based on everything I learned about SQL Azure so far.

I&#039;m also not asserting that it&#039;s a good design.  I&#039;m just pointing out that the structure of the docs was used to draw conclusions about quality of patch testing which seems to be unrelated.</description>
		<content:encoded><![CDATA[<p>The stuff that works is described in SQL Online Books, the regular dev docs that come with every edition of MSSQL.  So I believe the intent is to say &#8220;everything you know about MSSQL works except these few things and I&#8217;ll give you a link to a detailed description of them there so you know exactly what I&#8217;m talking about&#8221;</p>
<p>BTW, I&#8217;m not commenting from a position of authority (I don&#8217;t know the folks who made those decisions and I don&#8217;t work there). I was trying to help based on everything I learned about SQL Azure so far.</p>
<p>I&#8217;m also not asserting that it&#8217;s a good design.  I&#8217;m just pointing out that the structure of the docs was used to draw conclusions about quality of patch testing which seems to be unrelated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas LaRock</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1417</link>
		<dc:creator>Thomas LaRock</dc:creator>
		<pubDate>Sun, 18 Apr 2010 03:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1417</guid>
		<description>if a conscious decision was made to have those links included in order to show what is NOT supported, then that decision was wrong.

there is no way you can convince me that it makes sense to link to items you do NOT support, and then not link to something that you do support. that is the complete opposite behavior of anything i would describe as useful. i would rather think it was an oversight by someone as opposed to a strategic decision. if it was a decision then that person needs to be given the opportunity to participate in some usability seminars.

can you imagine if i showed my child pictures of four desserts they will NOT be eating after dinner? how silly would that be? and then, under my breath, i mention that we have some crackers for dessert but they have to climb up into the cupboard to get it themselves.

yeah, it&#039;s like that. it makes no sense to have built the site in that manner. someone needs to think simpler, and from an end-user point of view when it comes to documentation.</description>
		<content:encoded><![CDATA[<p>if a conscious decision was made to have those links included in order to show what is NOT supported, then that decision was wrong.</p>
<p>there is no way you can convince me that it makes sense to link to items you do NOT support, and then not link to something that you do support. that is the complete opposite behavior of anything i would describe as useful. i would rather think it was an oversight by someone as opposed to a strategic decision. if it was a decision then that person needs to be given the opportunity to participate in some usability seminars.</p>
<p>can you imagine if i showed my child pictures of four desserts they will NOT be eating after dinner? how silly would that be? and then, under my breath, i mention that we have some crackers for dessert but they have to climb up into the cupboard to get it themselves.</p>
<p>yeah, it&#8217;s like that. it makes no sense to have built the site in that manner. someone needs to think simpler, and from an end-user point of view when it comes to documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1416</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Sun, 18 Apr 2010 02:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1416</guid>
		<description>Ugh, in my prev comment I meant to write &quot;...you should not draw conclusions...&quot;</description>
		<content:encoded><![CDATA[<p>Ugh, in my prev comment I meant to write &#8220;&#8230;you should not draw conclusions&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1415</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Sun, 18 Apr 2010 02:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1415</guid>
		<description>Linking to DMV docs here is for the purpose of highlighting what is NOT supported so you have a good understanding of what&#039;s missing.

Why? Because one of the main issues with migrating to SQL Azure is that it supports a subset of features compared to SQL Server.  So the screen-shot above is intended to help evaluate migration rather than standard dev help.

What I&#039;m saying here is that you should&#039;ve draw conclusions on availability of dev docs and patching/testing policy based on this screenshot. Cheers!</description>
		<content:encoded><![CDATA[<p>Linking to DMV docs here is for the purpose of highlighting what is NOT supported so you have a good understanding of what&#8217;s missing.</p>
<p>Why? Because one of the main issues with migrating to SQL Azure is that it supports a subset of features compared to SQL Server.  So the screen-shot above is intended to help evaluate migration rather than standard dev help.</p>
<p>What I&#8217;m saying here is that you should&#8217;ve draw conclusions on availability of dev docs and patching/testing policy based on this screenshot. Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas LaRock</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1414</link>
		<dc:creator>Thomas LaRock</dc:creator>
		<pubDate>Fri, 16 Apr 2010 19:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1414</guid>
		<description>I have faith in you, Buck.</description>
		<content:encoded><![CDATA[<p>I have faith in you, Buck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buck Woody</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1413</link>
		<dc:creator>Buck Woody</dc:creator>
		<pubDate>Fri, 16 Apr 2010 17:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1413</guid>
		<description>Keep the faith - v1 is always v1. There&#039;s places to experiment and use this, and lots of places where it does not fit - but stay tuned, young man...</description>
		<content:encoded><![CDATA[<p>Keep the faith &#8211; v1 is always v1. There&#8217;s places to experiment and use this, and lots of places where it does not fit &#8211; but stay tuned, young man&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark S. Rasmussen</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1412</link>
		<dc:creator>Mark S. Rasmussen</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1412</guid>
		<description>@Brent Ozar
sys.dm_db_partition_stats should be enough to evaluate the size seeing as the size you&#039;re billed for is calculated from the number of active pages at any time. No concept of a data file or wasted space (except for internal fragmentation), only the number of pages matters.

@Thomas LaRock
I still don&#039;t get how they could launch Azure without any backup options. Sure, you can synchronize, but what about consistency? And if their solution to scaling is sharding, consistency becomes an even bigger issue - a workaround would be to make snapshots, but we can&#039;t do that either.

Their usual response to the traffic issue is to spin up a Windows Azure hosted script that retrieves and compresses the data before it&#039;s downloaded, since internal Azure traffic is free. Still a crap &quot;solution&quot; though.</description>
		<content:encoded><![CDATA[<p>@Brent Ozar<br />
sys.dm_db_partition_stats should be enough to evaluate the size seeing as the size you&#8217;re billed for is calculated from the number of active pages at any time. No concept of a data file or wasted space (except for internal fragmentation), only the number of pages matters.</p>
<p>@Thomas LaRock<br />
I still don&#8217;t get how they could launch Azure without any backup options. Sure, you can synchronize, but what about consistency? And if their solution to scaling is sharding, consistency becomes an even bigger issue &#8211; a workaround would be to make snapshots, but we can&#8217;t do that either.</p>
<p>Their usual response to the traffic issue is to spin up a Windows Azure hosted script that retrieves and compresses the data before it&#8217;s downloaded, since internal Azure traffic is free. Still a crap &#8220;solution&#8221; though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas LaRock</title>
		<link>http://thomaslarock.com/2010/04/sql-azure-woes/comment-page-1/#comment-1411</link>
		<dc:creator>Thomas LaRock</dc:creator>
		<pubDate>Fri, 16 Apr 2010 16:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://thomaslarock.com/?p=4037#comment-1411</guid>
		<description>oh, yeah, that is slick, huh? kinda like how they bill you for the data you will pipe and the only way to do a &#039;backup&#039; is to pipe data up and down.

still, it is no different than any other utility company.</description>
		<content:encoded><![CDATA[<p>oh, yeah, that is slick, huh? kinda like how they bill you for the data you will pipe and the only way to do a &#8216;backup&#8217; is to pipe data up and down.</p>
<p>still, it is no different than any other utility company.</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 10/37 queries in 0.015 seconds using disk: basic
Object Caching 569/603 objects using disk: basic

Served from: thomaslarock.com @ 2012-02-08 10:46:42 -->
