1. Trouble using identity ranges for subscribers of a merge replication
After the initial snapshot with the "DROP and re-create" option,
I remove the subscriber from the subscribers-list to edit the subscribtion
tables to have its specific identity range.
Then, I put the subscriber back on the subscribers-list and change the
snapshot option to
"Delete data in the existing table that matches the row filter". I also
leave the
"Include declared referential integrity on the primary keys" SELECTED!
When I run the re-sync, everyting is fine except the subscriptions table now
miss all the FK-relations, which were there before.
It looks like, that the "Include referential integrity" option is silently
connected to the
"DROP the existing table and re-create it" option.
But when I would use this option, I would loose the identity range settings.
A real dilemma!
So, currently I have to manually re-create the lost FK-relations.
Question:
Am I doing smth. wrong, or is it just the way it has to be?
Many thanks in advance.
Erd?l Biramen MCP+Internet, MCSE, MCSD, MCDBA, MCT
2. TPC-B or other Benchmarking utils??
3. Merge replication: state after problems at a subscriber
4. Setting the Paradox level parameter
5. merge replication conflict and identity range problem
6. Create indexes question
7. problem with merge replication and identity column
8. Please recommend a DB server for this...
9. Merge replication with identity value ranges using not for replication option
10. Merge Replication - subscriber not uploading
11. Merge replication deleting records on subscriber after sync
12. Merge replication, without replicate changes on the subscriber
13. Central subscriber and merge replication