Versioning SQL Server 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.]

Over time, the SQL Server Modeling Services database will require patches and minor updates. The Modeling Services database will also have major upgrades to new versions. Modeling Services uses different SQL Server features to accomplish both goals.

For patches and minor updates, Modeling Services will use standard database techniques to perform an in-place update. Future upgrades of the Modeling Services database require a more robust design that emphasizes the safety of existing Modeling Services data. An upgrade of the database must also minimize any downtime for dependent users and applications. Because of the increased risk associated with in-place updates for complex database changes, Modeling Services upgrades will use SQL Server Integration Services (SSIS). A SSIS package can move data from an older version of the Modeling Services database to an upgraded version of the Modeling Services database.

The use of SSIS in Modeling Services upgrade scenarios has several benefits. First, the original instance of the Modeling Services database remains unchanged. Applications that depend on the Modeling Services database can migrate to the new version of the Modeling Services database incrementally. Both of these factors minimize risk and downtime. It is also possible to include custom changes in the SSIS upgrade package. These modifications can be used to migrate an organization’s custom data in the Modeling Services database.

See Also

Concepts

Versioning Scenarios (Modeling Services)
SQL Server Modeling Services Administration