Comments
2 comments
-
I got it to correct itself finally. I had to add a column to the table which resulted in it creating a temporary table, copying all the data into the temp from the current table, dropping the current table, then renaming the temporary table. After that was completed I deleted the new column I added. This of course has a downside as associated history is lost because it now has a new Object_id.
-
Hi @Ed_Thompson
Thanks for reaching out to us regarding this!
I'm glad you have been able to find a workaround for this, however clearly you shouldn't have had to do this. Before I start to look at trying to reproduce this issue here, I wondered if as a very first step you could update to the latest version of SQL Compare to see if you still see the same issue? Version 14.4.20 can be downloaded from here: https://download.red-gate.com/checkforupdates/SQLCompare/SQLCompare_14.4.20.18129.exe
Add comment
Please sign in to leave a comment.
So my question is, what is the database looking at to validate the column name and how do I update that data?