title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | ||
---|---|---|---|---|---|---|---|---|---|---|---|
Deploy a Model Deployment Package (Wizard) |
Deploy a Model Deployment Package by Using the Wizard |
CordeliaGrey |
jiwang6 |
03/14/2017 |
sql |
master-data-services |
how-to |
intro-deployment |
|
[!INCLUDE SQL Server - Windows only ASDBMI]
Use the [!INCLUDEssMDSmdm] model deployment wizard to deploy packages that contain model objects only. If you need to deploy a package with data, see Deploy a Model Deployment Package by Using MDSModelDeploy.
Important
Packages can be deployed to the edition of [!INCLUDEssNoVersion] they were created in only. This means that packages created in [!INCLUDEssSQL11] cannot be deployed to [!INCLUDEssSQL14].
To perform this procedure:
-
You must have permission to access the System Administration functional area in the target [!INCLUDEssMDSshort] environment.
-
A model deployment package must exist. For more information, see Create a Model Deployment Package by Using the Wizard.
-
You must be an administrator in the environment where you are deploying the model. For more information, see Administrators (Master Data Services).
-
In [!INCLUDEssMDSmdm], click System Administration.
-
On the Model View page, from the menu bar, point to System and click Deployment.
-
On the Model Deployment Wizard, click Deploy.
-
Click Browse.
-
Find your deployment package (.pkg file) and click Open.
-
Click Next.
-
After the package is loaded, click Next.
-
If the model already exists, you can update it by selecting Update the existing model. To create a new model, select Create a new model and after you click Next you can type a name for the new model.
-
Click Finish to exit the wizard.
Notes:
-
If a subscription view in the package has the same name as a subscription view in an existing model, this warning is displayed: Deployer subscription view renamed. In addition, the view is created as modelname.subscriptionviewname. If this name is already in use, the subscription view is not created.
-
The deployment process has four steps:
-
The model objects are created.
-
Subscription views are created.
-
Business rules are created.
-
-
When creating a new or cloned model, if the process fails during any step, the model is deleted.
When updating a model, if the process fails during any of the first three steps, it does not proceed beyond that step; however, changes that are already made are not rolled back.
File attributes, and user and group permissions are not included in model deployment packages. After you deploy a model, you must update these manually. For more information, see: