Dropping wrong constraints

Jan 13, 2011 at 10:01 AM

Whenever I compare two databases and run the syncronize script it attempts to drop constraints with names from the origanal database rather than the one I'm trying to bring up to date.


ALTER TABLE [dbo].[FMPRMEXP] DROP CONSTRAINT [DF__FMPRMEXP__PC_IS___70B3A6A6] --------- This constraint is in the the old database and the new one is called DF__FMPRMEXP__PC_IS___1A4162CC

 I get the error

Msg 3728, Level 16, State 1, Line 1

'DF__FMPRMEXP__PC_IS___70B3A6A6' is not a constraint.

Msg 3727, Level 16, State 0, Line 1

Could not drop constraint. See previous errors.

Sep 5, 2011 at 6:55 PM
I haven't been able to reproduce this issue with the release currently in development (.9?).
I have attached a .sql script with a lot of constraints, all of which appeared to be dropped/created fine: