User Being Dropped in Target Environment

When deploying to another environment, SQL Change Automation may drop users from the target environment if those users don't exist in the source.

To work around this we recommend adding a filter to your release pipeline as outlined in the documentation page below.

https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/configuring-script-generation/filtering-database-objects

Quick Steps:

  1. Use SQL Compare to create a filter file excluding the users that are being dropped
  2. Save filter file to SCA project and name it "Filter.scpf."
  3. Add filter path in the SCA Release GUI or using PowerShell tool

(Note: If using Octopus Deploy, filter file must be saved to the Octopus tentacle of the target environment).

 

 

 

 

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request