You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the get-dbapermissions cmdlet evaluates all permissions on server level and in all databases.
Column level permissions are ignored and treated as the corresponding table permission. The cmdlet result shows the same table level permissions multiple times without referencing the columns.
I suggest to evaluate the minor_id in sys.database_permissions as well to create more complete view of permissions.
We currently use the GrantStatement column to document current permissions. This data is not correct in case of column level permissions.
I don't know how many other people use column level permissions. Maybe this is only a problem that strikes us in our special use case.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the get-dbapermissions cmdlet evaluates all permissions on server level and in all databases.
Column level permissions are ignored and treated as the corresponding table permission. The cmdlet result shows the same table level permissions multiple times without referencing the columns.
I suggest to evaluate the minor_id in sys.database_permissions as well to create more complete view of permissions.
We currently use the GrantStatement column to document current permissions. This data is not correct in case of column level permissions.
I don't know how many other people use column level permissions. Maybe this is only a problem that strikes us in our special use case.
Thank you for thinking about it
Tom
Beta Was this translation helpful? Give feedback.
All reactions