(This post was contributed by Reagan Templin, Lead Technical Writer for the MDS Team)
Recently, we released the first cumulative update (CU) for Master Data Services (MDS). This blog entry explains how to download and install that CU, as well as subsequent CUs for MDS.
Each Master Data Services (MDS) cumulative update is released as a stand-alone installer for SQL Server 2008 R2 Master Data Services. An update can be installed on a server without a previous installation of MDS, or it can be applied over an existing RTM installation or previously updated installation of MDS.
Note MDS is a feature of the versions and editions of SQL Server listed in Setup Requirements (Master Data Services) in SQL Server Books Online (BOL). Any computer where you install MDS must be licensed accordingly. For more information, refer to the End User License Agreement (EULA).
If your server does not have an existing MDS installation, you can follow the process documented in Installing and Configuring Master Data Services in SQL Server BOL. However, instead of running MasterDataServices.msi from the product media as directed in the documentation, run MasterDataServices.msi from the location where you extracted it in the download process above. Then create and configure the MDS database, Master Data Manager Web application, and MDS Web services as documented in SQL Server BOL.
If you apply an MDS cumulative update to an existing installation of MDS, you must run the installation package and then use Master Data Services Configuration Manager to upgrade the database.
Important Always test the update and upgrade process in a non-production environment before applying an update and upgrading the MDS database in your production environment.
If the update was unsuccessful, open Control Panel and use Programs and Features to uninstall Microsoft SQL Server 2008 R2 Master Data Services and then re-run the steps in this procedure.
After you apply the cumulative update and upgrade the database, start the Master Data Manager Web application, MDS Web service (if enabled in your environment), and any operations that you suspended prior to the upgrade process. Verify that your environment works as expected before you allow users to access the environment.