SSDT V11.1.50730.0 Using Schema compare to make changes from my development environment to a test environment (a copy of Production).
Part of the changes is the addition of columns to an existing table [Items]. The script that SSDT creates first drops foreign keys, creates and populates a temp [Items] table, then attempts to drop [Items] table. This produces the error:
Could not drop object 'dbo.Items' because it is referenced by a FOREIGN KEY constraint.
Is there some setting or reason that would result in the script generator to not include dropping and later recreating some of the foreign key constraints? Just wondering if it is something simple before I start manually modifying the script.