SQL Change Automation is always running the baseline script
I have an existing database in azure, lets call it dev. I set dev as the deployment target for my change automation project in vs 2017. I have a new database on my local machine. I run through the wizard and it deploys everything (Except data) down to my local machine. I save my projects and push back up to VSTS. In VSTS, I have a build pipeline that utilizes the Redgate SQL Change Automation Build step. This builds the project and creates the necessary package which is picked up by my release pipeline. The pipeline then runs a deployment of said package using the Redgate SQL Change Automation Release step. Each and every time, I get an error saying that a user already exists in the target database. If I pulled down the baseline from dev, should the script not run against dev, only new changes? It was my understanding that if there were already objects in the database the baseline script would not run. Please help, I have been trying to get this to work for two days now.
0 · Share on Twitter