SQL Change Automation adding permission assignments in the view script and creating schema for role

The project includes a filter that excludes users, roles and security policies. But the baseline script is including object permission assignments to users and roles. I edited the baseline (note that it was not yet checked into and not yet verified in the proj) . After removing the assignments from the baseline script then after the refresh some view scripts include permission assignments and one of the roles (excluded by default - since all roles are excluded) is being scripted as a schema.
What can I do to halt this behavior of assignments in the project, since all roles, users and security policies are removed?
This is related to another question I posted today, also (10/30/19).

tee October 30, 2019 16:56

Comments

1 comment

You should follow the instructions in the other thread on how to prevent SQL Change Automation from adding permissions when generating migrations: https://forum.red-gate.com/discussion/86088/baseline-includes-permission-statements-with-all-users-and-roles-excluded
In the case of Views this happens because they are Programmable Objects and as a result they will be in separate scripts inside the Programmable Objects folder, you will need to edit these as well.
If you still have issues after doing that please let me know.

Sergio R November 01, 2019 14:17

0

Add comment

Please sign in to leave a comment.

How can we help you today?

SQL Change Automation adding permission assignments in the view script and creating schema for role

Comments

Add comment