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

493 Views Asked by At

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?

1

There are 1 best solutions below

3
On BEST ANSWER

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.