Colin Brazier
asked on
How to resolve order of replicated articles so that dependent ones are done last?
Hi experts,
SQL Server 2008 R2
I am a beginner with replication and am trying to run merge replication on an entire database (tables, views, functions, SPs etc).
The snapshot generated OK, I created the subscription OK but cannot "propagate to the subscriber".
I suspect this is because it is trying to send, for want of a better word, the view definition before it has sent the underlying table(s). There are several interdependent views and tables, in the database; how do I resolve this?
Is it a question of several publications with different articles, run in a hierarchical order from the bottom up? Is there a system stored proc that can help me find what object is dependent on which others?
Thanks in advance,
Colin
SQL Server 2008 R2
I am a beginner with replication and am trying to run merge replication on an entire database (tables, views, functions, SPs etc).
The snapshot generated OK, I created the subscription OK but cannot "propagate to the subscriber".
I suspect this is because it is trying to send, for want of a better word, the view definition before it has sent the underlying table(s). There are several interdependent views and tables, in the database; how do I resolve this?
Is it a question of several publications with different articles, run in a hierarchical order from the bottom up? Is there a system stored proc that can help me find what object is dependent on which others?
Thanks in advance,
Colin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I worked it out in the end. First dependencies have to be found, then use sp_changemergearticle to set processing order for replication.
Regards
la