Model Deployment Options (Master Data Services)

In Master Data Services, when you deploy a model package file, you must decide whether to deploy a new or cloned model, or to update a model that was previously cloned.

When working with model packages, there are two primary workflows.

  • Create a package of a model in a test environment and deploy a clone of the model to a production environment. Over time, deploy updates from the test environment to the production environment.

  • Create a package of a model and deploy it as a new model to the same environment. In this case, you must give the model a new name.

In the MDS database, each model object has a unique identifier (ID). These IDs are included in model deployment packages. When you deploy the package, you must choose what to do with these IDs.

The following table should help you determine which choice to make when deploying a model by using either the System Administration model deployment wizard or the MDSModelDeploy tool.





Create a new model with a unique name. New identifiers are created for all model objects.

If you create a new model with new identifiers, you cannot use model deployment tools to apply updates to the model later. When using the wizard in the web application to deploy a model package, you have the option to create a new model only if a model with the same name or ID already exists.


Create a new model that is an exact clone of the model in the package. This works only if the model does not exist (by name or identifier) in the target environment. Use “clone” when you want to have the same model in multiple environments and update the cloned model over time.

This is the default behavior of the wizard in the web application. If a model with the same name or ID already exists, you are prompted to create a new model instead.


Update an existing model with the model in the package. The identifiers must be the same in both models. This is used to update a model that you previously cloned.

You can only update models that were previously cloned. (The names and IDs must match.)

Community Additions