Redmond Review

What's Old Is New Again

Aligning SQL in the cloud to SQL on the ground is about more than just common sense. It's about getting things done.

When I wrote my first column for this magazine 15 years ago, I covered a new advance in database programmability for Visual Basic programmers. I've been gone from these pages for a while, but I'm back. And, as an appropriate topic for a return engagement, I focus on another database programming advance, this time for .NET developers.

Back then, I explored something called the VB Compatibility Layer (VBCL), which let VB 3 programmers use version 1.1 of the Access/Jet Database Engine. VB 3 was the first version of the product to include its own database engine, and the VBCL ensured the newest version of that engine would be available to its programmers. Compatibility was key then, and it remains so today -- as Microsoft seems to have belatedly realized with its cloud computing strategy.

Last month Microsoft announced a major change of course for SQL Data Services (SDS), its cloud database offering. Although SDS is not yet released, Microsoft is nonetheless giving the technology a completely different programming interface than the one it announced more than a year ago. Back then, Microsoft brought us a product that, while based on a modified version of the SQL Server we all know, had to be programmed through an interface and conceptual paradigm that bore very little resemblance to it. Rather than giving us a database with tables, columns and T-SQL, Microsoft instead provided us with the "ACE" model: Authorities (which were akin to servers), Containers (akin to databases) and Entities (a cross between data records and dictionary objects). The ACE model didn't have tables, didn't require any consistent schema from Entity to Entity and could be accessed only through SOAP and REST Web service interfaces. Microsoft promised us relational capabilities for SDS, but appeared set on providing them by enhancing the ACE model, rather than just giving us direct access to the SQL Server behind the curtain.

The ACE model is good for basic storage and retrieval of data. Support for BLOBs means ACE works well for content management too. But for .NET application developers needing to do mainstream database work (in other words, almost all .NET developers), this first cut at SDS didn't make much sense. Microsoft had turned SQL Server into a structured storage repository instead of a relational database, and had implicitly told developers that if they wanted to move to the cloud, they'd need to re-design their databases and re-write their code. Ouch.

To call Microsoft tone deaf on this issue would be an understatement. But eventually the SDS team heard the music, and got the rhythm. On Feb. 23, at the co-located VSLive!/Microsoft Developer Conference in San Francisco, Microsoft hinted that they would re-jigger the SDS model to be relational, and on March 10 it announced through the SDS team blog that SDS would, in fact, be a cloud-based SQL Server, accessible via T-SQL over Tabular Data Stream (TDS), SQL Server's native protocol. Apparently, existing on-premises .NET/SQL Server code will work fine with the new SDS; only a change in connection string will be necessary to turn SQL Server code into SDS code.

So Redmond listened to its customers, and the bizarre obsession with copying Amazon's SimpleDB Web service is over. Microsoft has given us a truly simple offering: the SQL Server technology that most Microsoft developers have been using for a decade and some have been using since even before my first column was published.

What's old is new, I suppose. For database technologies as well as columnists. Aligning SQL in the cloud to SQL on the ground is about more than just common sense. It's about getting things done. Yes, the cloud, done right, will differ from on-premises technology. It will offer dynamic scaling and utility-based pricing. In short, it will lower the barrier to entry for getting applications up and running, and keeping them running smoothly. But the cloud, done right, will reflect and preserve familiar on-premises technology, too.

Because the cloud isn't just about how cool it is to run your application "up there." It's about easily provisioning the servers and services you need to run your business down here. SDS 1.0 had its head in the clouds; SDS 1.1 is appropriately down to earth. A compatibility layer indeed.

About the Author

Andrew Brust is Founder and CEO of Blue Badge Insights, an analysis, strategy and advisory firm serving Microsoft customers and partners. Brust is also a Microsoft Regional Director and MVP; an advisor to the New York Technology Council; and co-author of "Programming Microsoft SQL Server 2012" (Microsoft Press, 2012). A frequent speaker at industry events, Brust is co-chair of the Visual Studio Live! family of conferences and a contributing editor to Visual Studio Magazine. Brust has been a participant in the Microsoft ecosystem for over 20 years, and has worked closely with both Microsoft's Redmond-based corporate team and its field organization for much of the last 15. He is a member of several "insiders" groups that supply him with insight around important technologies out of Redmond. Follow Brust on Twitter @andrewbrust.

comments powered by Disqus

Reader Comments:

Add Your Comment:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above