MSSQL peer to peer replication what is the best practice to drop and create multiple table I have a Transactional Replication server in peer to peer topology with 3 server node.
My development strategy was Agile, so that will be a frequency change on the database etc.
Scenario: I need to drop 20 tables out of 100 tables, and create another 30 tables at a time.
May I know what is the best/common practice to do it?
What I can think of was,

Drop all replication article and subscription for 3 server node.
Drop the 20 tables and create the 30 tables on each server node.
Resetup back the peer to peer topology replication to the 3 server node.

(P/S: I am new in this replication technology, do guide me if my step is wrong.)
Yeah, this is the problem with Transactional Replication: every time you change something you need to recreate the publisher and the subscription.
I think your three steps are right.