NFR needed in Foreign Key constraint?

Chris,
have a look at this article:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/q
302/3/41.ASP&NoWebContent=1
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
That's great for one row, but reality is multiple rows can get updated.
Will the NFR work, what are my options? Doing a backup/restore to synch
subscriber, do I drop all FK contraints after restore and replace w/ indexes?
What is best practice? Subscribers used to offload reporting, so selects only
occuring against subscr.
Thanks,
Chris
"Paul Ibison" wrote:

> Chris,
> have a look at this article:
> http://support.microsoft.com/default.aspx?
> scid=http://support.microsoft.com:80/support/kb/articles/q
> 302/3/41.ASP&NoWebContent=1
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||My understanding is that to have TR work for a multi-row
update, you'd need to disable the FKs entirely.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)