mca blog

since i posted my personal views on Microsoft's announcement that SQL Data Services (SDS) will switch from HTTP/SOAP to TDS porotcol and drop the EAV model for the more traditional relational model, several rather helpful items have appeared. here are few that i think sum things up pretty well so far:

Microsoft Exec Explains SDS About-Face

In a surprise move, Microsoft said yesterday that it would expose its Tabular Data Stream (TDS) over-the-wire protocol for accessing SQL Server via its forthcoming Azure Services Platform. The move reverses the existing plan to offer SDS via the REST Web services interface. I spoke today with Niraj Nagrani, a senior product manager for SDS at Microsoft, about the changes.

First round of Questions and Answers

Tuesday was an exciting day for the team, and more importantly, for the industry. I think one of the best responses I got from someone was that they “stood up from their chair and did a dance of joy”. Here is the first round of questions I have received and the answers you are looking for.

SQL Data Services goes full relational

With SDS going relational not only you get to reuse all your knowledge and codebase in the cloud, but you also get all the benefits of a cloud-based infrastructure: high availability, piece-of-cake provisioning, pay-as-you-go growth, etc.

also, in a more NSWF vein, i read this one last night:

Having Your Head In The Cloud Is Better Than Up Your Ass

i think i know where my head is...