Comments on: From “Oslo” to SQL Server Modeling

By: Antoine Savelkoul |

Antoine Savelkoul | — Thu, 26 Aug 2010 10:20:24 +0000

[...] have missed it. Oslo , the codename for Microsoft’s new modeling platform, has been renamed to SQL Server Modeling. Confirms this that the focus will shift to SQL Server instead of creating a modeling platform [...]

By: Heikniemi Hardcoded » “Denali” to finally ship Oslo?

Heikniemi Hardcoded » “Denali” to finally ship Oslo? — Mon, 15 Feb 2010 15:12:15 +0000

[...] SQL Server Modeling, and the language M is also available to define other data structures. See Doug Purdy’s blog post for more [...]

By: Duchess | Women in Java Technology

Duchess | Women in Java Technology — Sun, 17 Jan 2010 14:09:04 +0000

[...] engineering vakgebied. Hoewel Microsoft het hiervoor ontwikkelde platform Oslo min of meer in de ijskast heeft geplaatst, lijkt de Java community met Eclipse serieuze stappen te nemen om een volwassen [...]

By: Bob

Bob — Fri, 08 Jan 2010 15:39:49 +0000

I predict that Oslo or SQL Server Modelling will be dropped within 2 years.

As for this being a tool to unify SQL, BizTalk, etc I’ve seen no evidence of this. Many people don’t even see a practical use of the tool.

It was a silly idea in the first place and just gave Don Box something to play with. Why don’t let just let Don go out to passure, COM+ was frankly your best work.. just leave it now.

By: Microsoft Will Demonstrate SQL Server Modeling At PDC 2009 | DatabaseProNews

Thu, 17 Dec 2009 19:55:17 +0000

[...] 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 [...]

By: skeptical

skeptical — Sat, 28 Nov 2009 03:42:42 +0000

this seems like a “you can’t handle the truth” situation. THe main point is that Microsoft – trhough CSD or whatever name it had before is full of pseudo gurus, “architects”, etc telling customer that they know what is better for you and what innovation looks like, when in reality they have no clue whatsoever. They try to look like they know what they are doing (usualy projecting the usual microsoft arrogant attitude), but they are really lost trying to “innovate” and convince people MS is still a “great” technology company. When you “squeeze” what is really comming out of these “innovations” you will find little to nothing to get “excited”, but they have to justify their big salaries, so relax and drink the coolaid.

same goes for entity framework, mobile fiascoS(emphasis on plural), WF “re-write”, etc.

Customers are the ultimate victims. I – for one, am sick and tired of these crappy, “upbeat” PR pieces. Get real.

By: PDC Traffic | PHP Scribe

PDC Traffic | PHP Scribe — Fri, 20 Nov 2009 20:35:20 +0000

[...] project was put together by a friend of mine Dana Kaufman, who works closely with the M/Oslo (now SQL Server Modeling) group. One of the black eyes of the Routing Service that I’ll get into at some point [...]

By: Michael Klotz

Michael Klotz — Fri, 20 Nov 2009 04:53:05 +0000

As a former MS partner, now customer (startup CEO), I am disappointed. Aside from substance of the move (which I let more technically inclined folks comment on), the name change sends the wrong message to MS customers, especially Enterprise customers.

Working with the CSD folks over the years, I really thought Oslo was the ONE for the Enterprise market and get it right. By right I mean really go after the platform, lock in the stack, have a compelling, integreated value proposition, be a leader and leverage all the great assets already in place (yes, I think BizTalk Server is great – great product, great value).
If Microsoft loses its foothold in the Enterprise over the years, we may well look back at this moment and say, ‘oh, this is when MS really missed the boat. This it could have been Microsoft’s big bet for the Enterprise, finally stepping out of the shadows of IBM, Oracle and SAP, putting it together beyond Windows, Office and SQL Server.’

Yeah, I know, it’s not 1995 anymore, but MS has to bet on something big for the Enterprise sooner or later. I’m sure the investment numbers are impressive in a nubmer of areas, including SSM. But what’s gone now is the inspiration of the Oslo vision. It made me belive that MS really gets it: how work is changing, how business is changing and how technology enabling these trends is evolving. I saw Oslo as all that. SSM just doesn’t do it for me. Sorry folks!

But then again, the underlying issue probably needs to addressed way beyond the great folks in the SQL Server and Oslo teams – this is steveb deciding between pleasing Wall Street next quarter or betting the company on something tha could be great. I’m afraid its the former. As a long term investor, I wish he’d pick the latter.

By: Jason Short

Jason Short — Thu, 19 Nov 2009 15:52:12 +0000

Wow, didn’t see that one coming. I thought it was a general purpose model language. My take away from previous sessions was that you could use it anywhere. Tying it into SQL Server seems like a very limiting scope to put all that power.

By: 3 Screens and The Cloud – PDC09

3 Screens and The Cloud – PDC09 — Wed, 18 Nov 2009 17:09:22 +0000

[...] Doug Purdy’s blog (owner of Modeling) and On DSLs and a few other [...]

By: Daniel COHEN-ZARDI

Daniel COHEN-ZARDI — Wed, 18 Nov 2009 15:28:57 +0000

The obvious conclusion is that Oslo will be tied to SQL Server.

For those interested in a model-driven aproach that would be more loosely coupled with implementation layers, one can have a look at CodeFluent.

By the way, we will support the different Oslo pieces on their applicable layer once they are available on the market.

Regards,

Daniel COHEN-ZARDI

By: SQL Server Modeling - the new name for Oslo - Johan Åhlén

SQL Server Modeling - the new name for Oslo - Johan Åhlén — Tue, 17 Nov 2009 15:07:44 +0000

[...] More information:http://www.douglaspurdy.com/2009/11/10/from-oslo-to-sql-server-modeling/http://social.msdn.microsoft.com/Forums/en-US/oslo/threads/ [...]

By: “M” & OSLO diventano SQL Server Modeling - Impedance Mismatch

“M” & OSLO diventano SQL Server Modeling - Impedance Mismatch — Mon, 16 Nov 2009 17:11:59 +0000

[...] http://www.douglaspurdy.com/2009/11/10/from-oslo-to-sql-server-modeling/ [...]

By: On “M” at Douglas Purdy

On “M” at Douglas Purdy — Sat, 14 Nov 2009 02:13:49 +0000

[...] couple of things related to “M” and respond to some questions that were posed in response to my From “Oslo” to SQL Server Modeling and On DSLs and a few other things… [...]

By: Xin Zhang

Xin Zhang — Sat, 14 Nov 2009 02:12:38 +0000

Rather than put everything under the SQL server nest, or BizTalk (later Dublin), would Microsoft consider creating a few products to accomplish all sorts of aspects in Enterprise SOA, ESB, BPM, complex event processing etc.

IBM and Tibco both have many products that specialized in something and can be used together to achieve a complicated enterprise solution.

Nowadays, Microsoft seems to be trying to create the SILVER bullet solution under SQL server for all. Very likely then, it may ends up do nothing well.

By: Andre

Andre — Fri, 13 Nov 2009 21:45:47 +0000

@douglasp

>retiring on the “Oslo” name is good thing from my

I don’t think that many developers here care that much about renaming only (although I think – Server Modeling or .NET Modeling without SQL would be better)

I think most of them (I too) care about:

a) Bundeling – if I use M-technology do I have to
ship SQL Server with my software ?

b) The announced CTP has as feature:
M – textual language ….. for SQL server
-> does that include or exclude the usage
of M as DSL tool for other areas but SQL ?

c) I think most of the developers assumed
Oslo technology would be decoupled from
SQL generally, but would also ship with
a layer which would allow a tight coupling
with SQL server. Why directly bind the
whole thing to SQL server directly.

To sum it up – I think (thought?) Oslo has (had?) a huge potential to leverage DSL/MDD technology in many areas of software development – including SQL server.
Now its potential seems to be restricted to SQL server only. Please say I’m totally wrong thinking that !

By: Joe Wood

Joe Wood — Fri, 13 Nov 2009 21:25:16 +0000

Doug – you’ve mentioned a few times how you think SQL Server is misunderstood and isn’t just a database engine. Could you provide some examples, or maybe point to some resources that explain what you mean?

For example, how can I use M to model SOA and synchronize the model with code in a source repository – if the model *has* to be in the database. Are you assuming the checkout is directly to a local SQL instance, or even SQL CE?

If this is out of scope for V1 in SQL Modeling then what is the plan going forward? Would you consider a separate sub-product to address the concerns of the commentors on this post? Maybe use the community in the same way as MVC has done? I would be interested in a FrontLine engagement if you feel there are still misunderstandings of the requirements or the products.

By: Alex

Alex — Fri, 13 Nov 2009 10:50:39 +0000

SQL Server Modeling
Hmm. . . SSM acronym is already well known for
Same Sex Marrige

Any chance we can roll back to Oslo? Windows 7 kept the development name, why not do the same?

By: Reflective Perspective - Chris Alcock » The Morning Brew #476

Reflective Perspective - Chris Alcock » The Morning Brew #476 — Fri, 13 Nov 2009 08:33:40 +0000

[...] From "Oslo" to SQL Server Modeling – Douglas Purdy talks about where Oslo came from, and what its future is looking like for the project, in the form of SQL Server Modeling, and that they will now ship with SQL Server [...]

By: digory

digory — Fri, 13 Nov 2009 04:06:36 +0000

>> I’ll add that I do think that we could learn to
>> be much more pragmatic in how we talk about these
>> things to customers.

Go back and watch the videos of you talking at PDC 2008 and ask yourself… what message should I have been trying to send.