"Matt Sradley" <MattSradley@discussions.microsoft.com> wrote in message
news:4C82B8F1-0176-4E6B-B0AF-D4F4F840A268@microsoft.com...
> We have a SQL Serrver 2000 database that utilizes merge replication. Every
> now and then the replication process attempts to insert or update tables
> out
> of order. For instance: We have a TransactionDocuments table that has a
> one
> to many relationship with a TransactionLines table. Sometimes SQL Server
> will
> attempt to instert new TransactionLines before it has inserted the
> TransactionDocuments the TransactionLines depend on.
>
> I thought merge replication was supposed to keep track of these
> dependencies. If so, is there a bug that has a workaround or something
> else I
> need to check?
>
> Thanks,
>
> Matt

"Hilary Cotter" wrote:

> Merge replication has a rich set of features regarding dependencies, but
> these are typically for sensing join filters. As Paul has pointed out child
> records can be inserted before parent records, but normally these are
> resolved within a batch and if not the next time the agent runs the
> dependencies will be fixed as the parent will get in before the child the
> second time around.
>
> The generic work around is to use the not for replication switch on all
> constraints.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Matt Sradley" <MattSradley@discussions.microsoft.com> wrote in message
> news:4C82B8F1-0176-4E6B-B0AF-D4F4F840A268@microsoft.com...
> > We have a SQL Serrver 2000 database that utilizes merge replication. Every
> > now and then the replication process attempts to insert or update tables
> > out
> > of order. For instance: We have a TransactionDocuments table that has a
> > one
> > to many relationship with a TransactionLines table. Sometimes SQL Server
> > will
> > attempt to instert new TransactionLines before it has inserted the
> > TransactionDocuments the TransactionLines depend on.
> >
> > I thought merge replication was supposed to keep track of these
> > dependencies. If so, is there a bug that has a workaround or something
> > else I
> > need to check?
> >
> > Thanks,
> >
> > Matt
>
>