Submit Your Article
At VS Connections, we learned that the long awaited modeling technology ‘Oslo’ would come to be known as SQL Server Modeling. There have been many opinions about this decision, with the descentors hoping for greater expansion out of the Microsoft’s new modeling tech.
For those who are still excited about SQL Server Modeling being released, the CTP sill be releasing the first day of the Microsoft Professional Developers Conference (PDC) at http://msdn.microsoft.com/data. Douglas Purdy, a Microsoft software engineer announced the good news on his blog.
There are three important functions of SQL Server Modeling, and Purdy provides us a glimpse of what each component consists of:
– “M” is a highly productive, developer friendly, textual language for defining schemas, queries, values, functions and DSLs for SQL Server databases
– “Quadrant” is a customizable tool for interacting with large datasets stored in SQL Server databases
– “Repository” is an SQL Server role for the the secure sharing of models between applications and systems
These aren’t the “official” names, as we’ll have to wait until a later date. Microsoft is hoping that with this new server model that interacting with databases will be an easier feat. The goal is provide a means for developers to quickly get their data down, and release an application within the shortest amount of time.
To coincide with the release, Microsoft will be highlighting numerous sessions and keynotes concerning the SQL Server Modeling. Purdy mentions a particular session to attend, “My personal favorite is “Active Directory on SQL Server Modeling” (the actual title is The ‘M’-Based System.Identity Model for Accessing Directory Services), which is going to show how a serious “ISV” is using these technologies.”
Many of the criticisms stemming from this announcement is that Microsoft will be pigeon holing themselves exclusively working with SQL. The detractors were hoping that Oslo would lead to better support of DSLs and LOP.
Purdy briefly discusses the decision for exclusively providing for SQL, “We learned that the folks on the SQL Server team were hearing the need for additional mechanisms to make the database more approachable to developers. Developers did not want use three different languages to build their database applications (T-SQL, a .NET language and a XML mapping file). Developers wanted new tools that let them deal with the truly massive amount of data they need to handle on a daily basis.”
Topics: Database, Programming, XML
