Setting Default value when Object mapping in Red-Gate Data Compare

Question

I am using Red-Gate Data Compare to synchronize two databases, lets call them DBSource and DBDestination. DBDestination has a table, TableA which has a field which has a not null constraint. TableA within DBSource has the same structure, apart from this new field.

When I synchronize using the Data Compare tool, it fails due to this particular not null field, since there's no object map I can set up for it.

I wanted to know if there is a way of setting a default on the tool, since I can't alter the schema of the destination table and the file is quite large to edit?

score 0 · Accepted Answer · answered Jul 07 '14 at 14:20

0

The best way to handle this is to alter the column in the database and put a default value on it. There isn't anything you can do in the SQL Data Compare settings to make it replace illegal NULL data with a default value.

answered Jul 07 '14 at 14:20

Wonko

331
1
5

This is what I ended up with. I think I might email the Red-Gate support to ask for this feature to be added. – Christian Phillips Jul 07 '14 at 15:45
1

Uservoice would be more effective. https://redgate.uservoice.com/forums/147879-sql-data-compare – Wonko Jul 08 '14 at 07:07
Already there, https://redgate.uservoice.com/forums/147879-sql-data-compare/suggestions/2973662-allow-copying-data-to-destination-that-may-have-no – Christian Phillips Jul 10 '14 at 08:16

Setting Default value when Object mapping in Red-Gate Data Compare

1 Answers1