This update fixes a number of issues related to the following areas in Microsoft SQL Server 2008 R2 Master Data Services. The following sections describe the fixes and functionality available after you apply this update.Hierarchy Management
Import and Export
|New members added to an entity in MDS while within a derived hierarchy will default the associated domain based attribute based on the user’s current location within the hierarchy.|
|In Explorer, the more option is available in the hierarchy tree for derived hierarchies.|
|Referential integrity is enforced for derived hierarchies with explicit caps.|Business Rules
|The staging process supports the deletion of members from an entity that supplies domain-based attribute values for another entity.|
|In Integration Management, under Unbatched Staging Records, the Model and Version drop-down menus enable successful selection of a different model and version.|
|The staging process is enabled for the Metadata model.|
|System member records from the Metadata model cannot be deactivated by using the staging process.|Attributes and Attribute Groups
|Business rules can now be deployed by using the Model Deployment wizard or API even if there are staging errors for file attributes.|
|Users can add multiple Actions to a business rule without causing the error, "Failed to enable constraints."|
|On the Edit Business Rule page, the contains the pattern condition and must contain the pattern action support up to 200 characters to allow for complex regular expressions.|
|On the Edit Business Rule page, users can use Delete from the right-click menu to delete a condition or an action without encountering the error, "An unknown error occurred."|
|The Internet Information Services (IIS) application pool identity no longer needs sysadmin privileges for the SQL Server Database Engine instance or db_owner privileges to the Master Data Services database to successfully publish business rules. Previously, insufficient privileges for the application pool identity resulted in the error, "A database error has occurred. Contact your system administrator."|
|Users can delete business rules that contain nested operators without specified conditions.|Versioning and Validation
|In Explorer, when entering a value for a numeric attribute, users can specify very long numbers without encountering the conversion overflow error, "A general error occurred. System.OverflowException: Conversion overflows."|
|In Explorer, when users edit numeric attribute values on the Member Information page, numbers following a decimal point are no longer rounded to two decimal places.|
|In Explorer, domain-based attribute values are retrieved from the database instead of from the cache. This enables new domain-based attributes values to be immediately available for an entity.|
|An attribute that belongs to more than one attribute group with different permissions now resolves as expected so that the least restrictive permission applies.|
|In System Administration, users can now reorder attribute groups without causing the attributes to disappear.|Users and Groups
|When a user copies a version, the member ID is preserved so that records can be compared across versions even if the member's code changes.|
|A new system setting, NotificationsPerEmail, has been added to specify the number of validation issues to include per e-mail when notifications are sent. This provides the ability to combine a number of validation issues in one e-mail rather than sending a separate e-mail for each validation issue.|
|Validation and copying versions is supported when two entities have references to one another (known as a recursive relationship).|
|In Version Management, on the Validate Version page, users can use the Model and Version drop-down menus to successfully select a different model and version for validation.|
|Validation issues are now properly removed after the issues have been fixed on the item edit page.|
|Validation issues have been improved to give more information about the issues found.|User Interface Usability
|In User and Group Permissions, on the Add groups page, users can add groups that contain a dash (-) in the group name.|API
|Drag and drop functionality has been fixed throughout the application so that it works when Master Data Manager has been added as a Trusted Site in Internet Explorer.|
|The hierarchy pane has been fixed to work properly with the minimum supported resolution of 1024x768.|
|Deletion of a metadata type is limited to one type in a single API call.|
Downloading and Installing the SQL Server 2008 R2 Master Data Services (MDS) June Update
This update is a stand-alone installer for SQL Server 2008 R2 Master Data Services (MDS) June Update. It can be installed on a server without a previous installation of MDS or it can be applied over an existing RTM installation of MDS. Note
MDS is a feature of the versions and editions of SQL Server listed in “Setup Requirements (Master Data Services)” at http://msdn.microsoft.com/library/ee633742(SQL.105).aspx. Any computer where you install MDS must be licensed accordingly. For more information, refer to the End User License Agreement (EULA).
To download the MDS June Update:
- At the top of this page, click View and request hotfix downloads.
- Read the terms of the agreement and click I Agree if you agree and want to continue.
- On the Hotfix Request page, select SQL_Server_2008_R2_Cumulative_Update_2_MD_Services to obtain this update.
Note Optionally, you can also obtain SQL Server 2008 R2 Cumulative Update package 2 by selecting one of the other options for your platform if you want to apply updates for other features and components of SQL Server 2008 R2. For more information about the fixes included with SQL Server 2008 R2 CU2, see "Cumulative Update package 2 for SQL Server 2008 R2" at http://support.microsoft.com/kb/2072493. The MDS June Update is not dependent on SQL Server 2008 R2 Cumulative Update package 2.
- Specify an e-mail address to e-mail this update to, and type the characters in the picture. Then click Request hotfix.
- On the Hotfix Confirmation page, review the information and wait for the hotfix e-mail to arrive.
- From the hotfix e-mail, open the link and download the .Zip file.
- Extract the .Zip file and provide the password included in the hotfix e-mail. MasterDataServices.msi will be extracted to the location you specify.
Installing MDS June Update on a server without an existing MDS installation:
If your server does not have an existing MDS installation, you can follow the process documented in SQL Server Books Online topic “Installing and Configuring Master Data Services” at http://msdn.microsoft.com/en-us/library/ee633752.aspx
. 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 Books Online.
Applying MDS June Update to an existing MDS installation:
If you apply the MDS June 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.
Before you start the upgrade process:
- Open Internet Information Services (IIS) Manager and stop the Master Data Manager Web application and the MDS Web service (if enabled). You can do this either by stopping the application pool that contains the Web application and service, or you can stop the Web site that contains them. If you stop the application pool, you stop requests for all applications in that application pool. If you stop the Web site, you stop only traffic to the Web site and any applications and services it contains.
- Stop any operations, such as scheduled jobs, that affect the MDS database.
- Take a current backup of the MDS database. If you are using the full recovery model, take a log backup immediately before you upgrade the database. If you are using the simple recovery model, take a full or differential database backup. For more information about backups, see Backup Overview (SQL Server) at http://msdn.microsoft.com/library/ms175477(SQL.105).aspx.
To apply the MDS June Update:
- On the server where you want to install this update, navigate to the location where you extracted MasterDataServices.msi and double-click it.
- The following message appears: A lower version of this product has been detected on your system. Would you like to upgrade your existing installation? Click Yes to proceed with the upgrade process.
- The Microsoft SQL Server 2008 R2 Master Data Services installation wizard opens. Follow the instructions in the wizard to configure installation options and then click Install.
- After installation completes, Master Data Services Configuration Manager opens so you can upgrade the MDS database.
- Click Databases, and then click Select Database. Connect to the database you want to upgrade. Once the database is selected, the following message appears: This database requires an upgrade. You cannot change system settings until the database is upgraded.
- Click Upgrade Database. The Upgrade Database Wizard opens. Follow the instructions in the wizard to upgrade the database and then click Finish.
- To verify that the database upgrade was successful, connect to the MDS database and query mdm.tblSystem. The value for SchemaVersion should be 18.104.22.168.
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.
for other considerations.