Microsoft Defends 'Oslo' Move to SQL Server
Since announcing its plans to fold its modeling technology, up to now known by the code name Oslo, into its SQL Server platform, Microsoft has been taking flak from developers complaining of a letdown by the software giant regarding the future of its modeling strategy. In response, Microsoft defends its plans and says the modeling strategy is intact.Since announcing its plans to fold its modeling technology, up to now known by the code name Oslo, into its SQL Server platform, Microsoft has been taking flak from developers complaining of a letdown by the software giant regarding the future of its modeling strategy. Indeed, developers commenting on the Microsoft blog post explaining the company's decision expressed views ranging from disappointment to feeling that Microsoft's move was "lame." Essentially, the primary complaints centered around Microsoft's decision to land the modeling technology in SQL Server, which many developers said they viewed as limited in scope. The other major concern was about the future of Microsoft's DSL (domain-specific language) technology as it relates to the "M" modeling language that is part of Oslo-now known as SQL Server Modeling.
Microsoft Software Architect Douglas Purdy, a leader on the Oslo project, blogged about the company's decision in a post that drew more than 40 comments. Those comments prompted Purdy to author a second post to further explain Microsoft's position.
"The key takeaway is that this is a SQL Server product feature that has programmability via .NET and VS. It is just as much a part of VS and .NET as anything else we ship. "As a developer, if you look at all the things you program against in VS/.NET you will [quickly] see that most of what you are programming are actually features of the underlying products like Windows, Office and SQL Server. ...
"The net of this post is the following: ??Ã The fact that these technologies are part of SQL Server does not mean that they are not available in Visual Studio or part of the .NET Framework-they are absolutely deeply integrated with both VS and .NET. ??Ã SQL Server, of all the Microsoft products, is the most obvious and logical place for these technologies to be located. ??Ã We remain committed to the core DSL capabilities of the "M" language."Moreover, in responding to developer comments on his first post, Purdy wrote, "If you have ever tried to ship a big v1 at a big software company, you know what this transition is and what it is like-and that this is a very positive step for customers and the team." And in summary, he added, "The great irony to all these comments is that all we did was change the name from 'Oslo' to ... SQL Server Modeling and now we get the #fail tag. If we had called it Windows Modeling or .NET Modeling would it have been #success?" Microsoft officials said the company will explain in more detail what the SQL Server Modeling move means at the Microsoft Professional Developers Conference, which runs Nov. 17 to 19 in Los Angeles.