SQL Server Performance

Peer to peer schema changes.

Discussion in 'SQL Server 2005 Replication' started by why, Oct 23, 2007.

  1. why New Member

    MS article says I need to stop all activity before I do schema changes.
    Can I stop activity on all peer to peer nodes except one that i'm making change on ?
    Can I add fields to existing tables under replication without stopping activity ? Do I need to stop "read" activity or only "write" activity ?
  2. ndinakar Member

    No you dont need to stop replication to do any schema changes. That beats the whole purpose of replication as a High Availability solution if you had to stop/restart it. Schema changes are replicated to the subscriber(s).
  3. why New Member

    I didn't mean stopping replication, but stopping activity on published tables. MS talks about "Quiescing a system". Is this just the precaution to make sure changes are in place on all nodes , and no outstanding replication storedproc calls are out there ? What if only one p2p node is really live and the other is just "syncing" ? Do I need to stop activity when adding article ?


Share This Page