Re: copying a database in real time.
From: Jerry Stuckle <jstucklex_at_attglobal.net>
Date: Sat, 20 Jan 2018 19:03:51 -0500
Message-ID: <p40lc3$5f7$1_at_jstuckle.eternal-september.org>
>>> bill
>>
>> That only happens if you're updating the slave. With a master-slave
>> relationship all updates should be done only through the master; the
>> slave can be used for fetching data.
>>
Date: Sat, 20 Jan 2018 19:03:51 -0500
Message-ID: <p40lc3$5f7$1_at_jstuckle.eternal-september.org>
On 1/20/2018 7:23 AM, bill wrote:
>>>>
>>>>
>>> The problem with using replication in this situation is that the
>>> slave (the new system) will create new records with new primary keys
>>> at the same time that the old system is creating new records with new
>>> primary keys which are then copied to the slave system causing a
>>> duplicate record error.
>>>
>>> I _think_ that master-master replication would work.
>>> bill
>>
>> That only happens if you're updating the slave. With a master-slave
>> relationship all updates should be done only through the master; the
>> slave can be used for fetching data.
>>
> > Correct, but in this case he was talking about having both create new > records > > -bill
Which is not a good idea. But this IS TNP, after all.
-- ================== Remove the "x" from my email address Jerry Stuckle jstucklex_at_attglobal.net ==================Received on Sun Jan 21 2018 - 01:03:51 CET