Discontinued Master Data Services Features in SQL Server 2012
This topic describes Master Data Services features that are no longer available in SQL Server 2012.
To make assigning security easier, you can no longer assign model object permissions to the Derived Hierarchy, Explicit Hierarchy, and Attribute Group objects.
Derived hierarchy permissions are now based on the model. For example, if you want a user to have permission to a derived hierarchy, you must assign Update to the model object. Then you can assign Deny access to any entities you don’t want the user to have access to.
Explicit hierarchy permissions are now based on the entity. For example, if the user has Update permissions to an Account entity, then all explicit hierarchies for the entity will be updateable.
Attribute group permissions can no longer be assigned in the User and Group Permissions functional area. Instead, in the System Administration functional area where attribute groups are created, users and groups can be given Update permission to attribute groups. Read-only permission to attribute groups is no longer available.
You cannot use the new staging process to:
Create or delete collections.
Add members to or remove members from collections.
Reactivate members and collections.
You can use the SQL Server 2008 R2 staging process to work with collections.
Model Deployment Wizard
Packages that contain data can no longer be created and deployed by using the wizard in the Master Data Manager web application. A new command line utility can be used instead. For more information, see Deploying Models (Master Data Services).
The wizard can still be used to create and deploy packages that do not contain data.
In addition, packages can be deployed to the edition of SQL Server they were created in only. This means that packages created in SQL Server 2008 R2 cannot be deployed to SQL Server 2012. You must deploy the package to a SQL Server 2008 R2 environment and then upgrade the database to SQL Server 2012.
Code Generation Business Rules
Business rules that automatically generate values for the Code attribute are now administered differently. Previously, to generate values for the Code attribute, you used the Default attribute to a generated value action in the System Administration functional area under Business Rules. Now, in System Administration, you must edit the entity to enable automatically-generated Code values. For more information, see Automatic Code Creation (Master Data Services).
If you have a SQL Server 2008 R2 model deployment package that contains a rule of this type, when you upgrade the database to SQL Server 2012, the business rule will be excluded.
Bulk Updates and Exporting
In the Master Data Manager web application, you can no longer update attribute values for multiple members in bulk. To do bulk updates, use the staging process or the Master Data Services Add-in for Excel.
In the Master Data Manager web application, you can no longer export members to Excel. To work with members in Excel, use the Master Data Services Add-in for Excel.
In the Explorer functional area, users can no longer revert their own transactions. Previously, users could revert changes they made to data in Explorer. Administrators can still revert transactions for all users in the Version Management functional area.
Annotations are now permanent and cannot be deleted. Previously, annotations were considered transactions and could be deleted by reverting the transaction.
The Master Data Services web service is now enabled automatically, as required by Silverlight. Previously, the web service had to be enabled manually.
MDS no longer includes PowerShell cmdlets.