Synchronization fails after renaming table
We changed the names of a couple of tables in our DB. When trying to synchronize our development DB to our test production DB we received errors that it couldn't create some constraints because they already existed and rolled back any changes. I had to manually rename the tables, re-run the compare and then run the synchronization. It then worked. Bug? Should SQL Compare 4 be able to handle it?
0 · Share on Twitter