I was just reviewing the Differences in our reporting database (subscriber) and it seems like the changes that I have made to the publisher (over several releases) have resulted in some Defaults and FKs being added despite the @schema_option settings.
My @schema_option = 0x00000004080350DF so has no Defaults or FKs since neither 0x200 (FKs) or 0x800 (Default) are set. Right?
Looks like despite the settings for the Publication that new columns are propagated with FKs and default constraints. A feature?
Q: Is there another setting somewhere to suppress FK, DF to match my selected Schema_Options (no FK, no DF), while still allowing wanted DDL changes like new columns to make it through? This is how I hoped it would have worked.
Is this or is it a known bug/limitation in transactional replication?
Is there a good reason behind this or is it just a limitation/bug?
Is it addressed in 2012?
SQL Server 2008R2
Thanks for your help.
...Ray
...Ray