disable and enable replication for software releases - whats the preferred method?
SteveL
we currently release new code/objects once a month into a replicated
environment....
1 warmstandby
4 replicants from a PRIMARY
4 Roll-up replicants - subscribing to the PRIMARY and their own
individual primary ( which is one of the replicants above ! )
( hopefully that makes sense ..)
In order to do the release, we disable replication on all primary's by
running sp_setreptable scripts.
( as well as previously quiescing the system etc. )
The release then applys any data modifications on each individual
database in the replicated environment. It's done this way so that any
large data modifications are not replicated and we don't rely on rep
server to replicate potentially millions of rows .
BUT... when we have completed the release, we have to obviously run the
sp_setreptable scripts to re-enable replication. This takes a long
while ... up to 1.5 hours due to a couple of very large tables
consisting of over 10 Million rows.
I'm going to look at other methods of doing this release without the
need for the sp_setreptable scripts, one of which will be to play with
the gen-id's in order to just purge any data that may be generated in
the queues during the release.
My question is, does anyone have any particular favorite
mechanism/procedure to do this kind of work? - am looking at this in
completely the wrong way?
Cheers.
Steve
A Cornell
you don't have to use sp_setreptable any where.
Another option turn off the replication truncation point
1. dbcc settrunc(ltm,ignore)
2, run updates
3, dbcc settrunc(ltm,valid )
4, exec rs_zeroltm "dataServer", "database"
"SteveL" <goo...@sybasedba.net> wrote in message
news:1168615545....@38g2000cwa.googlegroups.com...
Anders
If you are, why not just run 'set replication off' in the scrupts?
"SteveL" <goo...@sybasedba.net> skrev i melding
news:1168615545....@38g2000cwa.googlegroups.com...