Clever Geek Handbook

Diagrams Compare Visual Studio 2012

When I run compare and update using Compare Schema Compare Visual Studio 2012, I get "Unable to delete object" dbo.Countries because it is referenced by a FOREIGN KEY constraint. An error occurred during batch execution.

Now I understand this error and I could fix it manually. However, shouldn't the schema be compared when it creates a script account for it and drops the [constraint before trying to drop the table?

What's the point of this feature if we just need to fix something that Visual Studio was unable to account for? Am I missing settings?

+3


source to share


1 answer


I found several default db comparison settings there that exist for defensive purposes, but most of them can be overridden in the schema comparison options.



Take a look there and see if it helps resolve this for any future modifications.

0


source






More articles:


All Articles