Foreign Key cascades appear to be failing on publication causing conflicts.
Foreign Keys are set as Not For Replication
Several FK's on multiple tables point to 2 primary tables.
The Primary tables are set to replicate before their subordinate tables.
We recently upgraded our publication database from SQL 2005 to SQL 2012. Our subscriber DBs are 2005 Express. A majority of our tables are FK'd with upd/del cascade to 2 primary tables. Since the upgrade we've experienced a great number of conflicts because not all of the foreign key updates appear to be cascading fully. This appears to be isolated to Win 7 subscribers replicating against SQL 2012 because it was not occurring prior to the upgrade and it is only WIN 7 machines that are affected. It is not always the same tables that are affected and sometimes one of the primary tables is impacted while the cascades from it appear to have worked.
Has anyone else experienced a similar issue? Any ideas on what the cause may be and how to resolve the issue? Any help is greatly appreciated.