According to Hindsbro, partners want a full SQL Server database in the cloud. The current SQL Data Services (SDS), which became available last March, provides a lightweight and limited set of features.

Microsoft is still unclear on which RDBMS features they are thinking about. Gavin continues:

He did not say what SQL Server features Microsoft would add to Azure, other than to say it'll include greater relational functionality.
…
Microsoft in a statement also did not provide specifics, but said it's "evolving SDS capabilities to provide customers with the ability to leverage a traditional RDBMS data model in a cloud-based environment. Developers will be able to use existing programming interfaces and apply existing investments in development, training, and tools to build their applications."

The result of this [Microsoft] policy were schemaless EAV tables that offered flexible properties (property bags) in an Authority-Container-Entity (ACE) architecture that mystified .NET developers, who were then in the process of about-facing their mindset from traditional SQL queries to .NET 3.5’s Language Integrated Query (LINQ) constructs and object/relational mapping with LINQ to SQL and the Entity Framework. SSDS offered SOAP and REST data access protocols with a very limited query syntax.

Some important questions remains to be answered. Are Microsoft sacrificing scalability because existing customers want to utilize their existing knowledge? Or do they have a plan for architecting existing SQL Server technologies to scale in the cloud? What do you think?

Of course they are. How has the world survived so far with databases running on under 8 cores. Judging by these kinds of stories, it would seem impossible that any of them have managed at all. Most applications DO NOT NEED A THOUSAND SERVERS to host a data service. Microsoft are looking at using cloud farms for hosting traditional applications as well as the scale out stuff where SQL Server might not be appropriate but a combination of velocity with SQL Server must just work fine for a lot more and finally you have applications that need HBase,SimpleDB etc.

SQL is too complex and too low-level language, particularly, because it requires joins. Concept-Oriented Model (CoM) is a novel model which is join-free and has some features which make it rather interesting for cloud computing applications. In particular, it is easily distributed because all data exist in a virtual domain-specific address space. This model also has its programming counter-part: Concept-Oriented Programming (CoP). Thus programming and data modeling are two parts of one model. The both programming and data modeling approaches rely on the same new construct, called concept.