On Tue, 19 Jun 2007 08:18:14 +1200
David Kirk <[EMAIL PROTECTED]> wrote:

> Zane,
> 
> > I am giving a talk about SQL and possibly PHP at the next CLUG meeting.
> >
> > In an attempt to provide what people want, could you give me some
> > indication of what you want to hear about?
> 
> I'm looking forward to your talk.
> 
> I know you don't have any interest in System Administration, but I'd
> like to hear about dumping and loading databases.  I had to move a
> MySQL database from one server to another using phpMyAdmin.  The
> problem I had was that when the tables were very big, the import would
> timeout before it completed.
> 
> -- 
> Later
> 
> David Kirk

That's a php timeout, so is controlled by the relevant entry in php.ini on the 
target server. The only way round that it to use the command line, or to get 
the sysadmin on that server to up the timeout - it can be done for phpmyadmin 
alone, assuming apache is the http server in use.

If you can get command line access to the source server, then I recommend that 
you make 2 dumps of the database.

1. use the --no-data switch, so you end up with the database schema without 
data.
2. use the --compress --disable-keys --extended-insert --single-transaction 
switches, which will create a snapshot of the database, and it'll load the 
fastest.

This gives you the option of easily modifying the database on the new server ( 
no the table layouts, obviously! ) if the need arises.

My $0.02, but I've earned them the hard wat (:

Steve

Reply via email to