SSDT Data Comparison: Refresh does not detect newly eligible tables - by LeeC1791

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 811801 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/17/2013 7:50:42 AM
Access Restriction Public

Description

I created a new Data Comparison.  I noticed that some tables were not part of the comparison, but I expected them to be.  It turned out those tables had no PK set.  So, I set the PK on the target tables, then Schema Comparison synched it to the target.  I refreshed my Data Comparison, but the tables were still missing.  I tried "tickling" the source and target settings, but it did not help.  I closed the comparison and opened a new one using the "remembered" settings, and it picked up my newly eligible tables.
Sign in to post a comment.
Posted by LeeC1791 on 2/6/2014 at 7:34 AM
In that case, there should be a "refresh schema" function in the SqlDataCompare. I shouldn't have to close and re-open a data comparison to get a refresh of the schema.
Posted by Microsoft on 12/17/2013 at 7:58 AM
This is actually by design. Doing a full reverse of a schema could be very time-intensive (especially against SQL Azure) so we limit the scope of the refresh.