Printed 2017/08/19 08:37PM

Master Data Services: Versioning


In Master Data Services (MDS), you can create multiple versions of the master data within a model.  When you create a model for the first time, MDS creates a default initial version of your model data.  You can create as many versions you want for your model, either in sequential fashion (one version after another) or in simultaneous fashion (multiple versions in parallel).  This way you can ensure you have a dedicated/consistent version of your master data for downstream consumption while at the same time having another version for adding/deleting/modifying members or for testing your model data, without compromising consistency in master data availability.

You may want to have one version of the data marked as “current”, and another set marked as “proposed” (using Version Flags).  When the proposed version is confirmed as valid and clean, you can move that from proposed to current.

A version could be in either of these three status modes:

Here is a flowchart of all the modes:

Two important notes about using versioning:

  1. Creating a new version for a model causes a whole new copy of ALL the data in the model to be created, which could take a long time if you have a lot of data
  2. If you turn transaction logging on while staging, every change to the entity will be logged as a transaction.  Transaction logging is on by default when you use Excel or the web UI to add/edit members

More info:

Versions (Master Data Services)

MDS Versioning, Permission and Security

Video Microsoft MDS :: Version Management Part 1: Working with Versions

Copyright © 2002-2017 Redgate. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.