sys.fn_builtin_permissions should reflect the SQL Server 2014 permission inheritence - by Bob Beauchemin

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 800976 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/16/2013 9:41:48 AM
Access Restriction Public


The sys.fn_builtin_permissions function does completely reflect permission inheritance for the new SQL Server 2014 permissions. "Parent" refers to the parent_class_desc/parent_covering_permission_name columns, rather than covering_permission column.

Permission “USER/IMPERSONATE” should have a parent of “SERVER/IMPERSONATE ANY LOGIN”. It currently has no parent. Because having IMPERSONATE ANY LOGIN grants/denies impersonate permissions on all users. There is no IMPERSONATE ANY USER currently, which would be parent of IMPERSONATE USER.

Permission “SELECT” on “DATABASE” class should have a parent of “SERVER/ SELECT ALL USER SECURABLES”. It’s currently “SERVER/CONTROL SERVER”.
Sign in to post a comment.
Posted by Microsoft on 9/19/2013 at 5:46 PM
Thank you for submitting this feedback. We are investigating the issue and will update you when we have more information.