Comments
1 comment
-
Hi Robert,
Thank you for your forum post and sorry to read you had a difficult time deploying your database differences to the target database.
Normally, SQL Compare will deploy objects in dependency order. So I am interested in knowing further details on what occurred when you attempted to deploy.
What is the full version number of SQL Compare you are using? You can obtain this information from the GUI→Help menu →About option.
If known or seen, where there any warnings generated on the Summary page of the deployment wizard?
Many Thanks
Eddie Davis
Senior Product Support Engineer, Redgate Software Ltd
Add comment
Please sign in to leave a comment.
I've used SQL Compare forever. I've always used it to move objects over in an order I knew would be required due to dependencies. I had hoped it would have gotten better at automating the whole process and I could just hit the Deploy button on the top of the screen, but it was a mess. Before anyone says anything, I did have it set to include dependencies. However, it didn't hit them in the correct order. It also really did not like columns going from int to GUID.
I turned off the option to include dependencies and then I ended up using the tool running it in batches of objects that I knew would be okay, combined with some manual SSMS changes to move from a DEV database to QA
It was not an easy process. Instead of focussing AI on writing queries it would be much more useful if the AI effort was directed at making deployments more intelligent.
Another fun glitch was that the Deploy now button stopped working. However, closing the app and coming back in again brought it back.
I did manage to get the two databases sync'd so the tool is still really useful, but disappointing at the same time.