Hello everyone,
Sorry for the delay in responding but I had to be out of town for the last
4 days and didn't have access to my mail.
Here is a recap for those who are just joining:
I have multiple branch locations that need to have their transactions
rolled up into a common statistics database.
On Tue, 2004-04-13 at 13:13, [EMAIL PROTECTED] wrote:
[snip]
> >> I could frequently poll the slave servers using SHOW SLAVE STATUS or
> SHOW
> >> PROCESS LIST and watch for their status to change.
> >>
> >> I could start each slave with "--log-slave-updates" and watch the
> slaves'
> >> binlogs fo
> On Tue, 2004-04-13 at 15:11, [EMAIL PROTECTED] wrote:
>> On Tue, 2004-04-13 at 11:21, [EMAIL PROTECTED] wrote:
[more snip]
>> Somehow, I need to detect the
>> end of my central slaves' replication cycle so that I can trigger the
>> "merge processing".
> Its not clear what you mean by 'replicat
On Tue, 2004-04-13 at 11:21, [EMAIL PROTECTED] wrote:
> Hello List:
[snip]
> Here is where things get sticky. I would like to be able to merge the
> replicated reports into the warehouse database with the smallest practical
> delay (I have some very process-driven branch mangers and they feel they
Hello List:
I have been crawling the docs, the mailing lists, and the discussion groups
looking for options to my issues for several weeks and have found answers
to most of them. I have one last nut to crack and if the answer is out
there I must be blind. That's why I finally came to the list for
