Preventing Unique Constraints From Being Replicated

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Under SQL 2000 we have used sp_addarticle with the @schema_option =
0x00000000000080D3 to add tables to the publication. Using this option keeps
unique constraints from transferring over to the subscription, which is what
we want.

However, under 2005 using the same option doesn’t seem to work. In our
testing the unique constraints are being transferred over as unique indexes
to the subscriber. Has this option changed for 2005? What would be the
correct setting to prevent unique constraints from being replicated?


Thanks,
Mark
.