DAC and data compare still recreate constraints in database already syncronized
-
Thursday, February 25, 2010 8:12 AMhi,
seems a bug to me; here's a repro:
-backup northwind
-restore northwind with other name.
-remove a few order details rows in the new database
-compare both databases; it shows that are differentes
-syncronize boths databases; it will show there is no differences
-select "refresh update script", and then you'll see the drop and create constraint script.
Regards, Eladio
-- Moved by Sethu SrinivasanMicrosoft Employee Friday, November 02, 2012 12:21 AM SSDT - DAC (From:SQL Server Manageability)
All Replies
-
Thursday, February 25, 2010 6:06 PMhi Eladio, can you please file a bug on https://connect.microsoft.com
-
Wednesday, March 03, 2010 7:40 PMEladio,
I'm not sure that we completely understand the question.
The title to the posting says DAC (as in data-tier application component). Are you saying that you are working with the new data-tier application project system in Visual Studio 2010? And then using the schema compare/sync feature to push changes?
Are you seeing the same behavior in other database project types in Visual Studio?
Can you please elaborate on the type of project system in use?
Thank you,
Omri. -
Friday, November 02, 2012 5:08 PMOwner
It looks like you're referring to the schema compare offering from VS 2010 (also known as the "Data Dude" tools). These tools are no longer being worked on and SSDT is the replacement. Please upgrade to SSDT (http://msdn.microsoft.com/en-us/data/hh297027). Let us know if this issue repros in SSDT.
Thanks,
Janet
- Marked As Answer by Janet YeildingMicrosoft Employee, Owner Friday, November 02, 2012 5:09 PM

