<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - The Future of SQL Data Services with Nigel Ellis</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/466933_100x75.jpg</url>
		<title>Channel 9 - The Future of SQL Data Services with Nigel Ellis</title>
		<link></link>
	</image>
	<description>
I had the pleasure of sitting down with one of SQL Server’s brightest, Nigel Ellis, to discuss the future direction of SQL Data Services.&amp;nbsp; Nigel goes deep on the changes of SDS.&amp;nbsp; If you want to learn what’s really going on behind the scenes this is a great
 place to start.

Check out 
Nigel&#39;s MIX session here.

Follow the SQL Data Services team blog here. 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Wed, 19 Jun 2013 08:42:43 GMT</pubDate>
	<lastBuildDate>Wed, 19 Jun 2013 08:42:43 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[
<p>Is there any type of concurrency manager in the cloud ? </p>
<p>posted by Buzza</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764669850000000</link>
		<pubDate>Mon, 27 Apr 2009 22:09:45 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764669850000000</guid>
		<dc:creator>Buzza</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[10 Gigs really?&nbsp; I mean I have used 2TB databases. I think you will find people will really need at least 100 Gigs.&nbsp; Consiter something like Exchange backup&nbsp;where you got all kinds of emails and attachments being stored.&nbsp; Something like that NEEDS a large
 database cap.&nbsp; And the cop out of saying well you can create a bunch of little databases doesnt work as you cant run cross-database queries.
<p>posted by cdwatkins</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764708570000000</link>
		<pubDate>Mon, 27 Apr 2009 23:14:17 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764708570000000</guid>
		<dc:creator>cdwatkins</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[Buzza, for concurrently we have the same mechanism available to you as SQL Server.&nbsp;&nbsp; SQL support optimistic (timestamps or value comparisions) or pessimistic concurrency models.&nbsp; The presence of the Cloud doesn't change the model at all.<br>
<br>
Nigel.<p>posted by nigele</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764714060000000</link>
		<pubDate>Mon, 27 Apr 2009 23:23:26 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764714060000000</guid>
		<dc:creator>nigele</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[
<p>I agree there are cases where large databases are required.&nbsp; Your example of Exchange backup (or other backup scenario) is a case for large blob data.&nbsp; This is something supported using Azure blob storage - we will also be investigating supporting the SQL
 Server RBS interface which would allow seamless storage of large blobs alongside your structured data.&nbsp;&nbsp;&nbsp; 10GB of structured data is a great deal of information and covers our initial target application segments which shows most applications have databases
 in the order of &lt; 3GB in size.<br>
<br>
Remember any limits are just a starting point not an end.<br>
<br>
Thanks,<br>
Nigel.</p>
<p>posted by nigele</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764716390000000</link>
		<pubDate>Mon, 27 Apr 2009 23:27:19 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764716390000000</guid>
		<dc:creator>nigele</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[Really good.&nbsp; Thanks Nigel and great questions Zach.&nbsp; Am&nbsp;very happy to see move to TDS.&nbsp; I never could really bite into the soap SDS thing&nbsp;when I played with it, as simple actually became complicated because the model did not allow enouph flex.&nbsp; This new
 model will be great and being able to use SSMS makes so much sense and people will just get it.&nbsp; I also love the seemless integration with Astoria as&nbsp;it gives you a nice remote compute ability and rest.&nbsp; IMHO, large blob storage should be totally abstracted
 by the system.&nbsp; So a large varbinary(max) should just be stored in blob storage as needed and dev should not even know or care - it just appears as a varbinary and not counted in your 10GB (but maybe as table storage).&nbsp; I think a natural model is pay-to-play
 in terms of storage above 10GB.<br>
<br>
I also would vote for easy tenant virtualization in terms of applications.&nbsp; So I make a cloud app, but I need&nbsp;to support X different customers.&nbsp;&nbsp; I need each tenant/customer &quot;virtualized&quot; (and seperate)&nbsp;without having to update my tables and queries to support
 tenant IDs.&nbsp; All my queries &quot;route&quot; to proper virtual db based on login id.&nbsp; This would abstract uneeded complexity I think.<p>posted by staceyw</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764924230000000</link>
		<pubDate>Tue, 28 Apr 2009 05:13:43 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633764924230000000</guid>
		<dc:creator>staceyw</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[
<p>For all of the mortals out there (like myself) here is a link to some information about SQL Server 2008 Concurrency which essentials deals with how the SQL Server handles locking.<br>
<a href="http://msdn.microsoft.com/en-us/library/ms189132.aspx">http://msdn.microsoft.com/en-us/library/ms189132.aspx</a></p>
<p>Buzza, is there a particular situation unique to the Cloud that you are concerned about related to Concurrency?<br>
</p>
<p>posted by ZachSkylesOwens</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765549900000000</link>
		<pubDate>Tue, 28 Apr 2009 22:36:30 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765549900000000</guid>
		<dc:creator>ZachSkylesOwens</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[Nigel,<br>
10GB of &quot;pure&quot; data may sound like a reasonable starting point, but if the data are moderately indexed, the space would run out much-much faster.<br>
<br>
Are you planning to charge for the total consumed space (data and indexes), or table&nbsp;pages only?<br>
<br>
Are you planning to offer space compression by any chance?<br>
<br>
Seva.<p>posted by sokhaty</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765637980000000</link>
		<pubDate>Wed, 29 Apr 2009 01:03:18 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765637980000000</guid>
		<dc:creator>sokhaty</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[One other question.&nbsp; How will (if it will) the filestream type work.&nbsp; Normaly this stores it outside the database in normal NTFS.&nbsp; In the cloud would you have some kind of Azure Blob Storage that would store these files?&nbsp; Would they count twords the 10gig
 max on SDS?<p>posted by cdwatkins</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765778320000000</link>
		<pubDate>Wed, 29 Apr 2009 04:57:12 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633765778320000000</guid>
		<dc:creator>cdwatkins</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[
<p>&gt; Are you planning to charge for the total consumed space (data and indexes), or table&nbsp;pages only?<br>
The exact billing model is still under discussion.&nbsp; The size caps would apply to the physical database size so it would include all indexes defined.<br>
<br>
&gt; Are you planning to offer space compression by any chance?<br>
This is not currently in scope for our initial release.<br>
<br>
Nigel.</p>
<p>posted by nigele</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633766590730000000</link>
		<pubDate>Thu, 30 Apr 2009 03:31:13 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633766590730000000</guid>
		<dc:creator>nigele</dc:creator>
	</item>
	<item>
		<title>Re: The Future of SQL Data Services with Nigel Ellis</title>
		<description>
			<![CDATA[&gt;&nbsp;&nbsp;How will (if it will) the filestream type work.<br>
FILESTREAM (see <a href="http://technet.microsoft.com/en-us/library/bb933993.aspx">
http://technet.microsoft.com/en-us/library/bb933993.aspx</a>) will not be supported in SDS v1.&nbsp;&nbsp; There are some unique challenges with supporting this in our SDS cluster environment.&nbsp;&nbsp; We are however considering building a SQL RBS provider (see
<a href="http://msdn.microsoft.com/en-us/library/cc905212.aspx">http://msdn.microsoft.com/en-us/library/cc905212.aspx</a>) that would allow you to store blob data within Windows Azure and manage link level consistency from within SQL Data Services.<br>
<br>
Nigel.<p>posted by nigele</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633766592740000000</link>
		<pubDate>Thu, 30 Apr 2009 03:34:34 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/ZachSkylesOwens/The-Future-of-SQL-Data-Services-with-Nigel-Ellis#c633766592740000000</guid>
		<dc:creator>nigele</dc:creator>
	</item>
</channel>
</rss>