I am generating to SQL Server 2008 and I have a column on a table that I have checked the unique property for. This then is generated absolutely fine with the following sql:-
ALTER TABLE [workflow_instance] ADD CONSTRAINT [workflow_instance_uuid] UNIQUE ([workflow_instance_uuid])
However, when I come to generate a change script (from model to database), this shows up as a difference in the Sync and Convert Wizard - it says that the model column unique property is set to True and the reverse engineering column unique property is set to False (presumably because there is no actual unique property in sql server columns). It also shows the key itself as a difference by saying that the key workflow_instance_uuid does not exist in the reverse engineered model - which is also true as all that has been done is add a unique constraint on the column.
So it looks as though there is a discrepancy between what is generated and what is reverse engineered for unique columns in sql server 2008.
Is there something I can change, maybe in the model or in the reverse engineering settings, that will fix this false positive so that it understands they are one and the same thing?