Master Data Services subscription view permissions - by Gavin Campbell

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 776499 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 1/14/2013 9:07:48 AM
Access Restriction Public


It would be useful to have subscription views created in a separate schema (presumably in addition to the current MDM schema) in order to be able to grant select permissions on this schema to our Power(pivot, view) users, who query this data directly.

At present, the choices appear to be granting select permission on the MDM schema itself (which causes too much stuff to appear in the Excel dropdowns) or granting select permissions on individual views, which incurs maintenance overhead when new entities are added.
Sign in to post a comment.
Posted by Gavin Campbell on 1/22/2013 at 10:27 AM
It occurs to me that it might even be an idea to make these schema names user defined per subscription view; configurable from the create view dialog. This would enable separation between two different ETL processes (for example) that needed to access different subsets of the subscription views.
Posted by Lynn [MSFT] on 1/22/2013 at 10:21 AM
Hi SQLSophist,
Thank you for your feedback - this is an interesting request. We can consider how we might want to make this change, possibly for a future release. I will leave this item open for now. Thanks!