|
How reliable is using phpMyAdmin for dumping a ~600mb database into a mysqldump style output file? Normally I'd just ssh in and use mysqldump itself, but unfortunately this time around I don't have remote access for ssh (nor can I use a local mysqldump connecting to the remote db server, which is how I previously did what I'm trying to accomplish tonight.) Would this pose any risk of corrupting the existing data and/or abruptly stopping mid-process via a php time-out, corrupting the dump? I am, for all intents and purposes, a phpMyAdmin newbie and need to take the utmost care of this data.
|
#
¿
Dec 1, 2007 00:08
|
|
|
|
| # ¿ Apr 29, 2024 03:31 |
|
|
Kylratix posted:Yeah, that'll most likely fail. If you don't have SSH, take a look at your cpanel or what-have-you. Most hosts provide database backups through that as well. Yeah, I found the link inside cPanel for me to download the mysqldump output of the database in question which worked like gang busters. phpMyAdmin really is horrible, even after I got the database and did what I needed to do with it (namely trimming it down from 600 megs to 20, hooray for old apps that store images in the db), the re-import still didn't work all that well. I had to split the 15 meg .sql text file into 2 or 3 separate chunks to make it work properly.  Ahwell it's done at any rate, thanks for the help.
|
|
#
¿
Dec 1, 2007 23:41
|
|
|
When does "Using filesort" become a serious problem with MySQL? I've got a query that I want to have able to sort by an IF() statement in the SELECT parameters, and when I utilize that column in ORDER BY I get Using temporary; Using filesort. I'm not a huge DBA guy, but I know enough to know that "Using filesort" is basically like dirty language in church. Right now it's basically a non-issue AFAIK since there's only 2 rows in the table where the file sort occurs, but I'd rather fix it now if possible instead of being up poo poo creek when it becomes a major issue.
|
|
#
¿
Dec 29, 2014 21:17
|
|