How can we help you today? How can we help you today?

Ignore user permissions and role membership

I would like to take the opportunity to once again voice my issues with the option mentioned "Ignore user permissions and role membership".

Historically back in version 3 it was actually me who requested that these options be added. Obviously roles between dev/test/production environments will have different users in them, and we may not want to know that the roles are different for this reason.

There is also the need occasionally to filter explicit user permissions out, but still show permissions granted to roles. Once again this supports a model of using role based permissions across multiple environments.

Unfortunately these 2 options were combined together, whereas they really shouldn't be. There are use cases where one might be required without the other. eg auditing a production database against a snapshot (an automatic task i implemented which runs every morning for all of our databases), i dont want roles to show up as different due to the users in the role, but i definately DO want to know about all permissions, whether granted to a role, or explicitly to a user.

There have been several posts by myself regarding this over the versions... and im just hoping that finally with version 6 that we can maybe split these options to be 2 distinct ignore options.

Pretty please?

Here is a few of the old threads about it

http://www.red-gate.com/MessageBoard/vi ... php?t=2343
http://www.red-gate.com/MessageBoard/vi ... .php?t=687
rgribble
0

Comments

3 comments

Sort by
  • rgribble
    Not sure if this post fell off the radar, but given there has been no official response, im bumping it :)
    rgribble
    0
  • DavidBuckingham
    I wholeheartedly concur with rgribble's suggestion.
    DavidBuckingham
    0
  • JonathanWatts
    Hi there,

    Sorry about the delay in replying to this, I have had a chat with the developer concerned and I am afraid it is not good news. We cannot do this at the moment.

    Sorry to turn down this suggestion, but with the number of tweaks we have to do before the final release to other areas of functionality, we just don't have the time to do this safety and get it tested.

    I have updated the number of requests in the our feature request list, which is based on the number of unique requests we get for a feature. It has jumped up the list quite away. It is possible that it will make the next release, but it is still very close to the cut line so I cannot promise anything at this stage.

    Regards,

    Jonathan
    JonathanWatts
    0

Add comment

Please sign in to leave a comment.