Comments
4 comments
-
Well according to my trusty tester who has checked. We fixed a bug that could be that which you've found to do with the custom comparison key being on a field that contains a null value. We have fixed this in the next RC internally but it's unlikely that we'll released it as a 'beta'.
Can you just check if your varchar(255) field contains nulls in the source or destination as if there are any then it's certainly that problem.
Thanks. -
Hi Richard,
Have just looked and yes, there are nulls on both servers. Thanks for the quick response! 8)
Phil -
Thanks for confirming that so promptly.
Champagne has already been consumed. Buy it on monday.
-
Hi,
as Richard points out SQL Bundle 5 will be available on our web site on Monday 3rd April.
Thanks,
Tom Harris
Red Gate Software
Add comment
Please sign in to leave a comment.
I want to transfer a batch of records between servers but I can't use the ID field in the table (matching IDs on the target server have already been used for other things) , so I want to use a text field for comparisons instead. The field is a varchar(255) field. In Data Compare on the Project Configuration dialog I select the table, and select Custom in the Comparison Key column. In the comparison settings options, I uncheck the ID field and check the varchar field instead, then click Done on the dialog.
Data Compare tries to do some processing, and then in the dialog I get 'Tasks cannot be completed', and the message at the bottom is 'Object reference not set to an instance of an object'. Have I got a setting wrong, or is this an issue?
I found this this afternoon in the beta, I've updated to RC2 and the problem is still there
Phil Pursglove