[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Explicitly synchronizing source and target

  • Thread starter Thread starter ChUIMonster
  • Start date Start date
Status
Not open for further replies.
C

ChUIMonster

Guest
That seems like it ought to work but I worry about scenarios that I might be unaware of where maybe something doesn't get transferred. I was hoping for something more like "*will* do the trick" rather than "may do the trick" ;) The other problem is that in order for that to work without the possibility of those pesky users slipping in more transactions I think that I need a good way to kick them all out of the application without shutting it down. And not every application is going to make that easy. To expand on the use case a bit... I'm looking for a way to ensure that when I want to do something such as "flip" the source and target or pull a target out of replication and use it as a "clone" of production that I can be *certain* that there were no pending transactions that have not yet made it to the target. I'd like to not have to run multiple commands on multiple servers to do that or to verify that. I think that I need to shutdown the source db in order to ensure that all users have been disconnected and that no new transactions are started. But what I am not sure of is what, if anything, happens during the shutdown to try to bring both sides into sync.

Continue reading...
 
Status
Not open for further replies.
Back
Top