Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Deploy a Model Deployment Package by Using the Wizard

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Use the Master Data Services 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 note Important

Packages can be deployed to the edition of SQL Server they were created in only. This means that packages created in SQL Server 2012 cannot be deployed to SQL Server 2014.

To perform this procedure:

To deploy a model deployment package of model objects only

  1. In Master Data Services, click System Administration.

  2. On the Model View page, from the menu bar, point to System and click Deployment.

  3. On the Model Deployment Wizard, click Deploy.

  4. Click Browse.

  5. Find your deployment package (.pkg file) and click Open.

  6. Click Next.

  7. After the package is loaded, click Next.

  8. 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.

  9. 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:

    1. The model objects are created.

    2. Subscription views are created.

    3. 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:

Community Additions

ADD
Show:
© 2015 Microsoft