Ignore Permission Changes in Source Control
We are only interested in source controling the object definitions. We have a lot of volatile permission changes which we don't want to record, and its actually a hug obstacle constantly having to go in and check off 300 objects to commit just because someone changed a users permissions on them.
G$
shared this idea
SQL Source Control v3.0.5.7 has been released and allows you to configure comparison options – inlcuding ‘Ignore Permissions’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.
Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to do this: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521
Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.
If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.
-
Peter Forsberg-Madsen
commented
The suggestion 'Support SQL Compare Project Configuration' suggestion would also be able to solve this i think if you can chose to 'Ignore Users Permissions and Membership'
-
Kevin Reester
commented
And not just permissions. We need to be able to select which objects to source control and then do not even show the one's not shown. This could also improve performance as you would not need to look at objects that are not being controled.
-
Steffen
commented
Same Problem here - should be an option in the Setup for each linked database in my opinion.