Skip to content

upgrade-master-data-services.md

Latest commit

 

History

History
153 lines (84 loc) · 11.9 KB

upgrade-master-data-services.md

File metadata and controls

153 lines (84 loc) · 11.9 KB
title Upgrade Master Data Services
description Discover the four scenarios for upgrading Microsoft SQL Server Master Data Services. Learn about file locations and troubleshooting for upgrades.
author rwestMSFT
ms.author randolphwest
ms.date 06/03/2025
ms.service sql
ms.subservice master-data-services
ms.topic upgrade-and-migration-article
monikerRange >=sql-server-2016

Upgrade Master Data Services

[!INCLUDE SQL Server -Windows Only]

The following are the scenarios for upgrading Microsoft [!INCLUDE ssnoversion] Master Data Services.

[!INCLUDE support-notice]

Before you upgrade

Back up your database before performing any upgrade.

The upgrade process recreates stored procedures and upgrades tables used by [!INCLUDE ssMDSshort]. Any customizations you make to either of these components might be lost.

Model deployment packages can be used only in the edition of [!INCLUDE ssNoVersion] they were created in. You can't deploy model deployment packages created in [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], or [!INCLUDE ssSQL14] to [!INCLUDE sssql16-md].

After you upgrade Data Quality Services (DQS) and Master Data Services (MDS) to the latest version of [!INCLUDE ssnoversion], any earlier version of the MDS add-in for Excel no longer works. You can download the [!INCLUDE sssql16-md] MDS add-in for Excel from Master Data Services Add-in for Microsoft Excel.

File location

By default, the files are installed at <drive>:\Program Files\Microsoft SQL Server\<nnn>\Master Data Services, where <nnn> represents the [!INCLUDE ssnoversion-md] version. For example, [!INCLUDE sssql17-md] is 140, and [!INCLUDE sssql19-md] is 150.

Upgrade without Database Engine upgrade

In this scenario you continue to use [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md] to host your MDS database. However, you must upgrade the schema of the MDS database, and then create a current [!INCLUDE ssNoversion] web application to access the MDS database. After the upgrade, the MDS database can't be accessed by the earlier web application.

You can install the current [!INCLUDE ssnoversion] and an earlier version of [!INCLUDE ssnoversion] on the same computer. The files are installed in different locations, as shown in File Location.

  1. Install [!INCLUDE ssMDSshort] and any other features you want.

    1. Open the [!INCLUDE ssNoversion] Setup wizard.

    2. In the left pane, select Installation.

    3. In the right pane, select New SQL Server stand-alone installation or add features to an existing installation.

    4. On the Feature Selection page, select [!INCLUDE ssMDSshort] and any other features you want to install.

    5. Complete the wizard.

  2. Upgrade the MDS database schema.

    1. Open the current [!INCLUDE ssNoversion] [!INCLUDE ssMDScfgmgr].

      To upgrade the MDS database schema, you must be logged in as the Administrator Account that was specified when the MDS database was created. In the MDS database, in mdm.tblUser, this user has the ID value of 1.

    2. In the left pane, select Database Configuration.

    3. In the right pane, select Select Database and specify the information for your [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md] database instance.

    4. Select Upgrade Database to start the Upgrade Database Wizard. For more information, see Upgrade Database Wizard (Master Data Services Configuration Manager).

  3. Create a web application.

    1. Open the current [!INCLUDE ssNoversion] [!INCLUDE ssMDScfgmgr].

    2. In the left pane, select Web Configuration.

    3. In the right pane, from the Website list, select one of the following options:

      • Default Web Site, then select Create Application.

      • Create new site. A new web application is automatically created when the website is created.

      Your existing MDS web application from an earlier version of SQL Server ([!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md]) is available for selection in the [!INCLUDE ssnoversion] version of Master Data Services Configuration Manager. You must not select the existing web application, and instead must create a [!INCLUDE sssql16-md] web application for MDS. Otherwise, you receive an error when you try to associate the web application with the upgraded MDS database, stating that the requested page can't be accessed because the related configuration data for the page is invalid.

      If you want to use the same name (alias) for MDS web application as your existing ([!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md]) web application, you must first delete the web application and the associated application pool from IIS, and then create a web application with the same name using [!INCLUDE sssql16-md] version of Master Data Services Configuration Manager. For information about removing web application and application pools from IIS, see Remove an Application (IIS) and Remove an Application Pool (IIS).

  4. Associate the new web application with the upgraded MDS database.

    1. In the Associate Application with Database section, choose Select.

    2. Select the MDS database.

    3. Select Apply.

Upgrade with Database Engine upgrade

In this scenario, you upgrade both the database engine and [!INCLUDE ssMDSshort] application from an earlier version to [!INCLUDE sssql16-md] or a later version.

  1. For [!INCLUDE sql2008r2] only: Open Control Panel > Programs and Features and uninstall Microsoft [!INCLUDE sql2008r2] [!INCLUDE ssMDSshort].

  2. Upgrade the database engine to [!INCLUDE sssql16-md] or a later version. For more information, see Choose a Database Engine upgrade method.

  3. Complete all the steps in Upgrade without Database Engine Upgrade.

Upgrade in two-computer scenario

In this scenario, you upgrade a system in which SQL Server is installed on two computers: one with [!INCLUDE sssql16-md] or [!INCLUDE ssSQL17], and the other with an earlier version of [!INCLUDE ssNoversion].

If an earlier version of [!INCLUDE ssNoversion] is installed, you continue to use the earlier version to host your MDS database on one computer. However, you must upgrade the schema of the MDS database, and then use the [!INCLUDE sssql16-md] or [!INCLUDE ssSQL17] web application respectively to access the MDS database. The MDS database can't be accessed by the earlier version web application.

To upgrade in two-computer scenario

Upgrade by restoring a database from backup

In this scenario, either [!INCLUDE sssql16-md] or [!INCLUDE ssSQL17] is installed along with an earlier version on the same computer or two different computers. A database was backed up on a version earlier than the [!INCLUDE sssql16-md] or [!INCLUDE ssSQL17] release, before upgrade, and the database has to be restored.

  1. Install [!INCLUDE ssMDSshort] and any other features you want.

    1. Open the [!INCLUDE sssnoversion] Setup wizard.

    2. In the left pane, select Installation.

    3. In the right pane, select New SQL Server stand-alone installation or add features to an existing installation.

    4. On the Feature Selection page, select [!INCLUDE ssMDSshort] and any other features you want to install.

    5. Complete the wizard.

  2. Restore the database that was backed up.

  3. Upgrade the MDS database schema, create a web application, and associate the new web application with the upgraded MDS database. For the instructions, see steps 2 - 4 in Upgrade without Database Engine Upgrade

Troubleshooting

Issue: When you open the [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md] web application, a "client version isn't compatible with the database version" error message is displayed.

Solution: This issue occurs when a [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], or [!INCLUDE sssql16-md] Master Data Manager web application tries to access a database that has been upgraded to or [!INCLUDE ssSQL16] MDS. You must use a [!INCLUDE sssql16-md] or [!INCLUDE ssSQL16] web application instead.

This issue might also occur if you didn't stop and restart the MDS Application Pool in IIS when upgrading the MDS database schema. Restart the MDS Application Pool to correct the issue.

Related content