Do you have control over your DELETE queries? If so, 'SET SQL_LOG_BIN=0'
would be an easy implementation.
A common approach in my experience is to have a script query the master
and archive data to a second database before any deletes are done.
If you have no control over the DELETE queries and w
No, replication is not designed for this task.
It sounds like the Archive Storage Engine could be a good solution for you:
http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html
Robin Schumacher has written a nice introductory article:
http://dev.mysql.com/tech-resources/articles
Ian Collins wrote:
Hi,
I have a customer who wants to be able to replicate their live MySQL
database to a second server, but not to have any data deleted.
So there is data on the second server?
i.e., they want to accumulate the data.
I don't believe you can do this with replication. Does any
Hi,
I have a customer who wants to be able to replicate their live MySQL
database to a second server, but not to have any data deleted.
i.e., they want to accumulate the data.
I don't believe you can do this with replication. Does anyone know a way
of doing this?
Cheers,
Ian.
--
MySQL Gener
Hi,
I have a customer who wants to be able to replicate their live MySQL
database to a second server, but not to have any data deleted.
i.e., they want to accumulate the data.
I don't believe you can do this with replication. Does anyone know a way
of doing this?
Cheers,
Ian.
--
MySQL Gene
