September 25, 2017 at 10:12 am
I have a merge replication configuration. The publication database has a number of tables, some of which contain foreign keys. I build my subscriber database with exactly the same configuration as the publisher. All foreign key configurations are the same.
Once I add the new database as a subscriber of the publication database, a number of the foreign keys disappear.
Can anyone advise why this occurs and how I can retain the foreign keys?
Thanks.
September 25, 2017 at 10:20 am
Pete Bishop - Monday, September 25, 2017 10:12 AMI have a merge replication configuration. The publication database has a number of tables, some of which contain foreign keys. I build my subscriber database with exactly the same configuration as the publisher. All foreign key configurations are the same.Once I add the new database as a subscriber of the publication database, a number of the foreign keys disappear.
Can anyone advise why this occurs and how I can retain the foreign keys?
Thanks.
Could the 'not for replication' property be affecting this?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
September 26, 2017 at 3:25 am
Hi Phil. No, we're not using that setting and we do have schema changes enabled for replication.
September 27, 2017 at 4:35 pm
Pete Bishop - Monday, September 25, 2017 10:12 AMI have a merge replication configuration. The publication database has a number of tables, some of which contain foreign keys. I build my subscriber database with exactly the same configuration as the publisher. All foreign key configurations are the same.Once I add the new database as a subscriber of the publication database, a number of the foreign keys disappear.
Can anyone advise why this occurs and how I can retain the foreign keys?
Thanks.
Did you check the article properties for the publication and check the setting for Copy Foreign Key Constraints?
Also I don't think the foreign keys replicate if the referenced tables are not included in the publication
Sue
October 31, 2017 at 5:09 am
Sorry for the delay; forgot to update this.
This turned out to be a strange issue. The publication database had a number of duplicated foreign keys on several tables and I carried out a clean-up exercise to delete the unnecessary duplicates. However, when replication executed it processed the delete command and removed all of the previously-duplicated foreign keys. The only solution was to delete all foreign keys that were duplicated and then create the non-duplicated version of the keys again.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply