baseline includes permission statements with all users and roles excluded
tee
Posts: 25 New member
The project Filter is set to exclude all users and roles, (unchecked User and Role and Security Policy items' check boxes in the Filter list). SQL Compare 14 was used to create the filter. Role, User, Security Policy folders were not created in the project (this is as expected -- so the filter is partially working by excluding the generation of user, role and security policy folders and scripts). However, the baseline file contains permission assignments (at bottom of file) on objects to users and roles.
Examples of filter items in the Filter.scpf file:
Example: No filter (full inclusion):
Example Complete filter (full exclusion):
Examples of filter items in the Filter.scpf file:
Example: No filter (full inclusion):
<Sequence version="1">
<Include>True</Include>
<Expression>TRUE</Expression>
</Sequence>
Example Complete filter (full exclusion):
<User version="1">
<Include>True</Include>
<Expression />
</User>
Is there something that I can set in the filter to exclude the permission assignments of objects in the baseline script? Users and roles vary greatly between the different environments.
Is there something that I can set in the filter to exclude the permission assignments of objects in the baseline script? Users and roles vary greatly between the different environments.
Tagged:
Best Answer
-
Sergio R Posts: 610 Rose Gold 5You can do this by the setting the comparison options (which are applied when the migration script is generated):
https://documentation.red-gate.com/sca/developing-databases/concepts/advanced-concepts/comparison-and-script-generation-options
If you don't want to recreate the baseline, you can always edit it manually.
If I understood you correctly, you don't want any permissions and you are excluding roles in your filter, in that case the best option is to enable the IgnorePermissions option.
There's a similar option, IgnoreUserPermissionsandRoleMemberships, which is useful if you want to have permissions in your migration scripts but don't want to have users, in that case you would assign permissions to roles and just filter out users.
Sergio
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools