SQL Data Services Update - from IndyPass

Tonight's IndyPASS had some great information about the upcoming changes to Sql Data Services. For those who haven't read my other posts about SDS, it's a great emerging technology that moves your database into the cloud. I'd recommend that you really begin to look into this... in the coming years, it'll be tougher and tougher to host many of your app's databases in house.

Below are my basic notes from this week's meeting--they are scribbles, nothing more--but feel free to read 'em. Oh, regular readers, you'll note that this is a significant change in direction. Primarily--the ACE model is no more. True T-SQL and a SQL Server in the cloud. Hurrah?



Data Sync

Microsoft has committed to offering a bilateral data sync for SQL Server 2008 to and from Sql Data Services.

Accessible from many languages including Java, Ruby, and PHP. Of course, this includes .NET

TDS is not nearly as efficient as Rest/Http calls--they'll be additional latency added by making calls to the server, however hopefully you'll reap the gains from the clustered data centers that Microsoft'll be offering through it's "SQL Server Fabric".

Provisioning Model...

Account - Each account has a billing relationship with Microsoft and ownership of one or more Virtual Servers.
Server - One or more databases including Virtual Master. Each database limited in size. One or more logins.
Database - One or more Sql Users
Server = server1.data.database.windows.net

No comments: