Skip to content

Latest commit

 

History

History
80 lines (51 loc) · 3.95 KB

File metadata and controls

80 lines (51 loc) · 3.95 KB
title Deploy a Model Deployment Package (Wizard)
description Deploy a Model Deployment Package by Using the Wizard
author meetdeepak
ms.author dkhare
ms.reviewer mikeray
ms.date 03/05/2026
ms.service sql
ms.subservice master-data-services
ms.topic how-to
ms.custom
intro-deployment
build-2025
helpviewer_keywords
deployment packages [Master Data Services], deploying
models [Master Data Services], deploying a package

Deploy a Model Deployment Package by Using the Wizard

[!INCLUDE SQL Server - Windows only ASDBMI]

[!INCLUDE support-notice]

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

Prerequisites

To perform this procedure:

To deploy a model deployment package of model objects only

  1. In [!INCLUDEssMDSmdm], 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.

Next Steps

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:

See Also

Deploying Models (Master Data Services)