SQL Server Performance

Updating PKs on Replicated Table

Discussion in 'Performance Tuning for SQL Server Replication' started by photura, Jun 6, 2006.

  1. photura New Member

    I've been given the task of updating the data in the PK column of a table that is being replicated using Transactional Replication.

    What impact will this have on the subscriptions? Will the change get replicated without a problem?

    What would be the best and easiest way to handle this?
  2. photura New Member

    I should probably add to my post that there are many FKs. Maybe a cascade? How would replication handle that?

    Thoughts are appreciated.
  3. photura New Member

    Can somebody please offer some advice on this? I'd appreciate it.

    What I really need to know if how will replication handle a cascade update on the data of a PK column?

    Is the best way to update the PK field of a replicated table to take the table out of replication, drop all FK's, update the PK data, do the same on all subscribers and then add everything back into replication?

    Thanks.


    quote:Originally posted by photura

    I should probably add to my post that there are many FKs. Maybe a cascade? How would replication handle that?

    Thoughts are appreciated.

Share This Page