Douglas Purdy

When we announced at the components of “Oslo” would ship in a future version of SQL Server, a common question was “Does that mean that I can only use these components with SQL Server?”.

I know it is hard for some people to hear the name “SQL Server” and think anything more than “relational engine”, but it is so much more.

The reality is that SQL Server, for lack of a better brand, is our overall data/information management offering that spans more scenarios than you can shake a stick at.

In addition, this offering is used through the entire Microsoft platform, from Windows, to SharePoint, to System Center, to Dynamics.

If there is data involved, you can bet components of the “SQL Server” are being used.

What does this mean for our modeling technologies? Only good things.

This means that our approach to modeling will get widespread adoption throughout the Microsoft internal and external ecosystem that uses SQL Server.

Want to see an example of an end-to-end scenario?

Go http://microsoftpdc.com/Sessions/KEY01 and jump to 1:57:00 in the presentation.

That is SQL Server Modeling in action.

Visual Studio and System Center working together over a common model (written in “M”) in stored in SQL Server Modeling Services.

This capability will add tremendous value to customers and it is brought to you through SQL Server and our investments in “Oslo”.

Want to see another example?

Go watch the video for The ‘M’-Based System.Identity Model for Accessing Directory Services.

Again, this is going to add tremendous value to customers and it is brought to you through SQL Server and our investments in “Oslo”.

To but a bow on this, go read: Oslo transforms into the underlying application model of the cloud.

At PDC, after I explained the above, most people understood what we were doing with SQL Modeling, but two questions seemed to remain.

First, “How do I use these technologies in my application?”

Second, “This seems like a bunch of Microsoft internal stuff, can I just get the DSL stuff?  Oh, and please don’t say SQL Server around me”.

The former question is straightforward to answer.

If you use a database or XML to drive your application, our modeling technologies can help you a great deal.

Most ISVs that we talk with are already “model-driven” using either a database or XML files, but they effectively roll their own modeling platform.

SQL Modeling provides modeling capabilities that these ISVs can leverage, just like Microsoft “ISVs” are doing today.

These same capabilities that make model-driven applications possible, also help with applications that deal with lots of operational data.

This is one of the core reasons that we have brought “M” and EDM together and started to leverage the Entity Framework and Data Services.

You can model your application’s domain in “M” and get a wonderful conceptual model that you program against in VS/.NET.

The latter question is straightforward too.

Ignore the name SQL Server and check out the bits.

If we are doing something stupid and we are blocking you from using the DSL part of “M” in the way you want, send us the feedback.

I think you will find that enabling a DSL ecosystem is an important aspect of what we are trying to do.

“M” is a language for data – and we ship our implementation language with the Microsoft data offering – which for better or worst, we call SQL Server.

Lars is after me to come up with a better name for SQL Server/SQL Azure – which I am working on…

I am running the Big Sur Marathon this year.

I have run more than my share of half-marathons (13.1 miles), but this will be my first full length event.

Based on my reading, if there is one marathon to do in North America modulo Boston, Big Sur is it.

I am at the end of my training arc and I have happened upon an approach that I am going to use moving forward.

Half-marathons on MWF each week (doing this now), one marathon per month run on a Sunday with the week following off.

I don’t know if the week off is going to be enough, but I did 22 miles the other day and it took me two down days to recover, so I hope 8 days is fine.

I’ll be taking photos and tweeting from the event, as it is my excuse to walk up H. Ridge, so you can share in the adventure.

This also let’s me tell people if I need some to pick me up.