SQL Server Modeling Services
The “Repository” now has an official name: SQL Service Modeling Services.
This name continues our tradition of naming functional components beyond the core engine with the services moniker.
Other such services are Reporting Services, Analysis Services, Integration Services, etc.
Shosh will be talking more about it at PDC at SQL Server Modeling Services: Using Metadata to Drive Application Design, Development and Management.
We are still working on the official names for “Quadrant” and “M”. We have some good candidates, but we didn’t get to close for PDC.
Just as a reminder:
“Oslo” –> SQL Service Modeling
The components of the SQL Server Modeling are:
- “M” is a highly productive, developer friendly, textual language for defining schemas, queries, values, functions and DSLs for data
- “Quadrant” is a customizable tool for interacting with large datasets stored in SQL Server databases
- SQL Service Modeling Services (nee “Repository”) is a SQL Server role for the the secure sharing of models between applications and systems
Douglas: In your latests posts, in my opinion, a key piece of OSLO is missing.
What is the new name & place for OSLO MGrammar?
Will it be supported or is missing in the transition to SQL Server Modeling Services?
Thanks.
Pedro J. Molina, PhD
18 Nov 09 at 22:32
@pedro: MGrammar is the name that we used at PDC 2008 for the grammar part of the “M” language. We now refer to that as the language part of the specification. Net-it is just part of “M”.
douglasp
19 Nov 09 at 01:00
LOL. And so the recovery phase commences… Seriously, this is a step in the right direction after the recent debacle. People will accept that the repository, and quite possibly Quadrant, naturally belongs as part of SQL Server. They will *not* use M if they think it is tied to your database product. Frankly they won’t use it unless it remains free of charge. So, whatever name you choose for M, cut the ‘SQL Server Modeling’ moniker and, if at all possible, give a strong undertaking to keep it free of the SQL Server license. People want modeling technology at the level of the entire Microsoft platform, and not just one part of it. If you do that, you should be able to recover some of the ground lost in the last week or two.
jedR
19 Nov 09 at 18:12