The issue is that conceptual data models designed by application developers and the physical schema of databases are often different. Astoria sets out to simplify access to data, both relational and non-relational using web services, with an initial mapping layer that starts with the obligatory object-relational mapper. The next piece is the brain surgery: providing a way to automate mapping the developer’s view of the data to what exists in reality.

Initially, ADO.Net for Data Services is being developed for the relatively stripped down REST style of web services. For now, it was developed to simplify RESTful access to SQL Server, Oracle, MySQL or other relational databases. In the long run, Microsoft wants to make this the core engine for a variety of data services over the web, which could include reporting or analytic services.

But the technology, still in its infancy, clearly wasn't ready for the debut of Visual Studio 2008, previously c ode-named Orcas. But it should make it into the next update of VS 2008, which is likely sometime in Q2.

The ADO.NET for Data Service preview is being released in conjunction with ASP.NET 3.5, which supports a simpler use case. That’s where you are designing a web app that goes against a single SQL Server database. ASP.NET 3.5 adds a new MVC (model view controller) feature as part of an incremental upgrade.

---