<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx</link><description>After Paul Nielsen post SQL in the Cloud yesterday I decided to put on my Nostradamus hat and give you my take on this. What needs to happen before we can move to the cloud? There are a couple of things, here is a partial list Performance has to be good</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12209</link><pubDate>Wed, 25 Feb 2009 17:01:23 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12209</guid><dc:creator>jamiet</dc:creator><description>&lt;p&gt;&amp;quot;The ability to upload a file and specify the target object to load the data into has to be implemented. We get files via ftp all the time, nobody wants to parse the files locally and insert row by row.&amp;quot;&lt;/p&gt;
&lt;p&gt;Denis,&lt;/p&gt;
&lt;p&gt;I wouldn't worry too much about this - I'm sure there'll be tools available. In some cases there already is - you can already download a free SSIS destination adapter for SDS - i.e. A component that uploads the contents of a SSIS dataflow into SDS.&lt;/p&gt;
&lt;p&gt;-Jamie&lt;/p&gt;
</description></item><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12210</link><pubDate>Wed, 25 Feb 2009 17:07:28 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12210</guid><dc:creator>Morris Lewis </dc:creator><description>&lt;p&gt;The medical center I work for is private, and you don't even have to limit statement about the acronym soup requirements to public companies. There is simply no way health care organizations are going to trust their data and their ability to provide their services to a third party they don't control. The risk of impacting patient safety and the loss of money and goodwill is far greater than any benefit the cloud may offer. I can see companies creating their own clouds, especially if it improves uptime or offers better disaster recovery solutions, but that's the only way I can see clouds being more than Microsoft's current &amp;quot;golly, look at what our research dept cooked up this week!&amp;quot;&lt;/p&gt;
</description></item><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12222</link><pubDate>Wed, 25 Feb 2009 23:10:24 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12222</guid><dc:creator>James Luetkehoelter</dc:creator><description>&lt;p&gt;I think Morris' comment is dead on - the biggest issue with a the Cloud concept when it comes to information (not processing) is one of trust. A &amp;quot;cloud&amp;quot; implies something unknown or undefinable happening. That's why you have a network diagram that ultimately leads to a &amp;quot;cloud&amp;quot; icon if you're hitting an external network system (which isn't necessarily the Internet).&lt;/p&gt;
&lt;p&gt;I know of many private companies that have 200MB databases that would never trust an outside agency to host it without being able to ultimately &amp;quot;point&amp;quot; to that data (&amp;quot;it's on server x at our location B that also has data for 1000 other customers).&lt;/p&gt;
&lt;p&gt;Cloud computing I think is an inevitability - cloud data an oxymoron. Data I believe must reside on a discrete island, with a discrete &amp;quot;owner&amp;quot;.&lt;/p&gt;
</description></item><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12249</link><pubDate>Thu, 26 Feb 2009 07:39:06 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12249</guid><dc:creator>Kasper de Jonge</dc:creator><description>&lt;p&gt;Well my guess is that cloud computing will take flight soon, think MS Azure and SSDS, it will make hosting .NET websites in the cloud with data from webservices rather simple (as far as i can see)&lt;/p&gt;
</description></item><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12301</link><pubDate>Fri, 27 Feb 2009 14:27:41 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12301</guid><dc:creator>Jason</dc:creator><description>&lt;p&gt;This makes this cloud more interesting to me.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.theregister.co.uk/2009/02/23/sql_server_azure/"&gt;http://www.theregister.co.uk/2009/02/23/sql_server_azure/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: SQL Server In The Cloud Vaporware Or Inevitable?</title><link>http://sqlblog.com/blogs/denis_gobo/archive/2009/02/25/12206.aspx#12392</link><pubDate>Mon, 02 Mar 2009 17:33:39 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:12392</guid><dc:creator>Bikerdad</dc:creator><description>&lt;p&gt;Perhaps its time to re-read William Gibson's &amp;lt;i&amp;gt;Neuromancer&amp;lt;/i&amp;gt;. &amp;nbsp;It's not that much of a step from the Internet to Clouds to full blown Cyberspace. &amp;nbsp;What is pretty much a given in terms of tech advances is this:&lt;/p&gt;
&lt;p&gt;If you can see it on the horizon, and it looks like a 'slam dunk', its gonna take a LONG time. &amp;nbsp;Anybody got their flying car yet? &amp;nbsp;It's the things that come out of nowhere that move fast.&lt;/p&gt;
&lt;p&gt;&amp;quot;scattered clouds&amp;quot; is the way of the near (5-20 yr) future. &amp;nbsp;Physical security issues, bandwidth, and legal are the primary challenges. &amp;nbsp;Outside of the theoretical sciences, too much of the data that intensive crunching applications use is subject to privacy concerns, whether legal (i.e. medical data), or proprietary (does Company X really want its engineering prototype info in the cloud?). &amp;nbsp;High volume low criticality stuff will make it to the cloud first, which means entertainment. &amp;nbsp;Porn clouds, music clouds, etc. &amp;nbsp;The problem with these is the bandwidth issues.&lt;/p&gt;
</description></item></channel></rss>