I love tools like phpMyAdmin, but trying to perform mysql import or export commands on a remote server can sometimes be infuriating. It might work, it might not. You shouldn't have to ask "Will it succeed this time? Safari's been spinning for awhile... maybe it's dead...". You have better things to do.

Don't be afraid of mysql commands

need to import your DB?

mysql -u DATABASE_USER -p -h HOST DATABASE_NAME < FILE.sql

dumping a DB? almost the same command only in reverse

mysqldump -u DATABASE_USER -p -h HOST DATABASE_NAME > FILE.sql

You can take it one step further and timestamp your dumps using the Unix date command.

site_name_$(date +%Y-%m-%d-%H%M.%S).sql

the above would produce something like site_name_2009-01-07-1122.39.sql

The above flags translates to interface with MySQL with the user (-u) and prompt for a password (-p) on a specific host (-h), Then import/dump FILE.sql to/from DATABASE_NAME.

For DB imports and dumps, you will need to have permission to 'LOCK' the DB

This is all pretty trivial stuff but it will shave quite a bit of time off your day if you take the long path and go for the GUI. Time is money, you should be making it and moving on to better things, rather than waiting for operations like DB imports.