Compares and synchronizes SQL Server databases, backups and scripts.
Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong
I have been working on a solution to only deploy certain users and their permissions as part of a Continuous Delivery effort.
In my experiment I follow these steps:
1. Set up comparision of SVN codebase vs empty DB.
2. Set the filters to exclude everything
3. Set filters to only include certain users (example: @name like 'dev\\%' ) and
4. Set filters to include all roles
Result: the users filtered out still appear under the roles and therefore the generated deployment script will fail due to the "missing" users.
I am also curious of what best practices or recommendations do you have for handling users when they are only supposed to be deployed to certain environments, but I think I will post that question in the RGDM forum.
A good example would be denying testers from prod access.
BÃ¡lint Bartha, Skyscanner
- Posts: 10
- Joined: Mon Apr 07, 2014 2:38 pm
Usually this is a question of adding some options as well as excluding the users and roles objects - you can try adding the "Ignore User Properties and Role Memberships" and see if that helps. The users could be getting pulled in as part of a role.
Sorry I don't have a concrete answer - this always ends up being an environment-specific issue but when it comes to this very common user problem, it's usually related to a dependency that needs to be filled for a permission or difference in role membership.
- Posts: 6669
- Joined: Mon Aug 23, 2004 10:48 am
Return to SQL Compare 10
Who is online
Users browsing this forum: No registered users and 0 guests