My response intermixed...

"Denis Gerasimov" <[EMAIL PROTECTED]> wrote on 03/30/2005 09:29:00 
AM:

> 
> > >
> > > Hello list,
> > >
> > > I have two MySQL 4.1 servers, one local and one remote. I need to
> > transfer
> > > database from one server to another. What actually is the best way 
of
> > > handling this task?
> > >
> > > Are there any standard MySQL tools available for doing that (I mean
> > MySQL
> > > Administrator/Query Browser etc.)

Have you looked at mysqldump and mysqlhotcopy?

> > >
> > It's not clear from your question whether you want to transfer the 
data
> > once
> > only or if you want to transfer it repeatedly, perhaps daily or 
weekly. If
> > you mean the latter, you may want to look into MySQL Replication, 
which
> > enables all the changes made to the data on one server to be 
automatically
> > made to the other server as well.
> 
> Well, I need this only time to time, just for transferring data when I 
need.
> 
> 
> I assume that that is a bad idea to copy db files from one server to
> another. mysqldump is not an exciting option too...
> 
> But there is a simple solution when using MySQL Administrator: make 
backup
> of desired data to SQL file, then connect to another server and restore 
it!

That is exactly what mysqldump does for you.

> 
> > 
> > I haven't used MySQL Replication but I know it exists and is 
documented in
> > the MySQL manual.
> > 
> > Rhino
> > 
> > 

Replication would be a possible solution if you needed to keep the two 
databases in synch. Since this is only a periodic update, replication is 
probably overkill for this issue.

I seriously think you should check out mysqldump. For one-off or 
infrequent transfers, I think it works just fine. Especially since you 
already said that you think that writing the schema and data to a SQL file 
was a preferable idea....

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine



Reply via email to