Comments
Sort by recent activity
Hi Asha,
Thanks for commenting.
Sorry if I wasn't clear: the constraint in the target database is not being recognized.
The target column is displaying in the comparison as:
[PublicHousing] [bit] NOT NULL
but in reality is:
[PublicHousing] [bit] NOT NULL CONSTRAINT [DF_Interview_PublicHousing] DEFAULT ((0))
which is exactly what is in the source column.
Since the comparison doesn't see the constraint it generates ALTER statements for these which fail as the constraint already exists.
This is happening throughout our comparison on multiple tables. It is only on constraints where a default value is being generated.
Thoughts? / comments
Hi Asha,
Thanks for commenting.
Sorry if I wasn't clear: the constraint in the target database is not being recognized.
The target column is displaying in the comparison as:
[PublicHousing] [bit] ...