SSDT Bug - Error when renaming tables and then columns - by thebread

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 777806 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/29/2013 2:46:39 PM
Access Restriction Public


We are in the process of renaming existing tables (and a few columns within them) and then creating views to mimic the old table/column names.  I got stuck for a few hours getting an error when I would try and compare the project to my local DB.  After spending a few hours sifting through the refactor log I was able to find a workaround.  If I dropped all of the new views (that mimic the renamed tables/columns) I was able to get the compare to complete and then apply all the changes at once.

The error I was getting: "Object reference not set to an instance of an object"
Sign in to post a comment.
Posted by thebread on 2/28/2013 at 10:40 AM

I believe that I am using the latest (December - v11.1.21208.0). I have had the same thing happen to me a couple times since I made this post. It could be that it only happens when the Compare/Update fails for some unrelated reason (like I am adding a not null column with no default) and then I attempt to run it again. In that scenario I have to drop the views from the DB and then rerun the Compare/Update in order to get past the issue/error.

Posted by Microsoft on 2/27/2013 at 5:13 PM
I can't reproduce the issue with the steps that you provided. I use the most recent SSDT build.Which SSDT build that you are using? The most recent SSDT build might fixed this.