Versioning Scenarios (Modeling Services)
[This content is no longer valid. For the latest information on "M", "Quadrant", SQL Server Modeling Services, and the Repository, see the Model Citizen blog.]
SQL Server Modeling Services has several versioning scenarios. The topics in this section provide guidance on managing these scenarios.
Versioning Overview
Versioning in Modeling Services can include any of the following areas.
| Versioning area | Description |
|---|---|
Modeling Services Database |
This involves an upgrade of the Modeling Services database. This upgrade must emphasize the protection of existing Modeling Services data and minimize any disruption of access for users and applications. |
Modeling Services Schemas |
Schemas for Modeling Services data models evolve over time. Schema authors should minimize the number of application changes that must be immediately performed after a schema update. |
Application Lifecycle Management |
Application development based on Modeling Services data requires integration with source code control systems (SCCS). Modeling Services will support file-based synchronization techniques to provide this integration. |
Application Versioning |
Applications store data in the Modeling Services database. This data is spread across tables, related to the same Modeling Services Folder for that application. Modeling Services folders provide flexibility for upgrade scenarios. |
In This Section
The following topics discuss versioning strategies for the Modeling Services database and for Modeling Services schemas within the database:
See Also
Concepts
SQL Server Modeling Services Administration
SQL Server Modeling Services Architecture