Change Data Capture

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. Nigel goes deep on the changes of SDS. If you want to learn what’s really going on behind the scenes this is a great
place to start.
Check out
Nigel's MIX session here.
Follow the SQL Data Services team blog here.
Is there any type of concurrency manager in the cloud ?
I agree there are cases where large databases are required. Your example of Exchange backup (or other backup scenario) is a case for large blob data. 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. 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 < 3GB in size.
Remember any limits are just a starting point not an end.
Thanks,
Nigel.
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.
https://msdn.microsoft.com/en-us/library/ms189132.aspx
Buzza, is there a particular situation unique to the Cloud that you are concerned about related to Concurrency?
> Are you planning to charge for the total consumed space (data and indexes), or table pages only?
The exact billing model is still under discussion. The size caps would apply to the physical database size so it would include all indexes defined.
> Are you planning to offer space compression by any chance?
This is not currently in scope for our initial release.
Nigel.