Hi sol,
sol beach wrote:
I have limited experience with MYSQL replication; which is why I am hoping
others with more experience can answer a question or two.
Let's say I have a MASTER MYSQL database.
Let's say there are 50 - 60 other systems where I'd like to have MYSQL
running on these "slave" systems.
These slave systems need to be kept in synch with the Master, but it does
NOT need to be anywhere near real time.
The data in the slaves could lag as much a an hour or two.
The amount of data in total in the MASTER is in the range of 100MB - 250MB
The rate of changes to the data is in the range 2000 - 5000 DML per 24 hour
day.
We control the application so we can/will include date/time each record is
created or modified.
You can assume that no records ever get physically deleted; only INSERT &
UPDATE (no DELETE).
What are some alternative ways to keep the slave systems "current"?
The best, easiest, simplest way to do this is just to use MySQL's built-in replication.
Once you learn its (many) strengths and (relatively few) weaknesses, it works
extremely well.
If you want to avoid some of the gotchas, I have written about my experiences
here:
http://www.xaprb.com/blog/2007/01/20/how-to-make-mysql-replication-reliable/
Hand-rolling replication is a bad idea in my opinion, so I don't have any alternative
methods to suggest. However, if you just need to sync some data efficiently, try MySQL
Table Sync (http://mysqltoolkit.sourceforge.net/).
Cheers
Baron
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
