Skip to Content

Replicate a primary database in 3 diferents secondaries dbs

Jun 02, 2017 at 09:58 PM


avatar image


I want replicate a primary database in three diferents dataservers, so have 3 copies.

My doubt is about the sincronization ¿ Can I follow 3 times the same procedure as I have oinly one promary to a single secondary ?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Mark A Parsons Jun 02, 2017 at 11:58 PM

If you need to do the syncs one-at-a-time (eg, you can't take all 3x RDBs offline at the same time) then yes, you could just perform each sync using the same steps you currently use for a single-PDB/single-RDB setup; and if you're using a dump marker method then you'll need to perform 3x PDB database dumps (once for each sync)


If you want to perform the 3x syncs in parallel (and you can afford to have all 3x RDBs offline at the same time) then it'll depend on how you plan on performing the sync (and how long each sync will take).

If you plan on using a dump marker method (eg, create connection/use dump marker -or- resume connection/skip to resync marker + sp_start_rep_agent/resync), and you can perform the 3x syncs at the same time, then you should be able to run a single 'dump database' command in the PDB and use the resulting dump file to sync all 3x RDBs. You'll just need to make sure all 3x RDB/DSIs are suspended with a status of waiting for a dump marker *before* you perform the PDB database dump.

If you attempt to sync all 3x at the same time via a dump marker method, just make sure you watch your stable queue space usage as all 3x RDB/DSI queues are going to fill up with PDB activity while waiting for the 3x RDB loads to complete and the 3x RDB/DSIs to be resumed. If the stable queue(s) hit 100% utilization (ie, no more room in the repserver queues) then the PDB repagent won't be able to clear the PDB log, which means the PDB log would then start to fill up, and of course if the PDB log hits 100% full then all PDB write activity comes to a halt until log space can be free'd up (or the log extended).


Actually, during any lengthy RDB/sync process you need to keep an eye on stable queue space usage to make sure you don't run out of room; if you start to run out of room you have a couple options a) add space to the SRS stable queue (if you add partitions, you can always drop them later once no longer needed) or b) plan on performing the sync during a time when you can expect a reduced volume of activity coming out of the PDB.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Very Clear. Fortunately the database is not big, and I can synchronize together.

Thank's a lot