As I don't have Adminer in front of me right now, I can't be 100% sure, but it does sound like things have changed since my previous post. It's sounds like the options are now under "Import"?! The limitation to 16MB, is most likely coming from the PHP config, so updating to a (much) larger "max upload" (and restarting the webserver) may well allow you to upload your file (although perhaps Adminer also creates a limit).

Re using the Adminer "run" functionality, a few things come to mind. First up, judging by the filename, I assume that you have gzipped the file? If not, please change the name back to .sql.

Next up, for security, Adminer runs under the webserver user account (www-data). So the file will need to be somewhere where Adminer can look (i.e. that www-data has access to), as well as have the appropriate permissions to do something with it. By default, files you upload using the root account will be owned by root.

Personally, I'd recommend that you just use the commandline. But I get that many aren't super keen to do that. If that is an option for you and assuming that you are using a v15.x TurnKey appliance, and depending on how you created the sql dump, something like this should work:

mysql -u root db_name 

If for some reason that fails, please feel free to post back with the command you used and the result. Also if you can tell me which appliance this relates to, the version you are coming from and the version you are going to, hopefully I should be able to point you in the right direction. In the meantime, I just did a quick google and turned up this. The question relates to MySQL commandline on Windows, but a quick browse through the answers suggests that commands are generic and should work on Linux too.

You may also need to make some other adjustments to get everything to work (including adding a user, updating passwords, etc). So for assistance with that, again, I'll need more info...

If you'd rather persevere with Adminer, then please read on...

As a general rule, the www-data user has full access to the /var/www directory and all sub-directories below that. So that's probably the easiest place to put your file. Although please note that if you are using the LAMP, Nginx or LigHTTPd appliances (or any appliance that has been configured to have access to /var/www as it's doc root), that file will now be downloadable by anyone! If that's the case, putting it somewhere else (and ensuring that www-data has full access) would be a better idea. If that's the case, then possibly the best bet is to rename your file to a random name so it's unlikely that anyone will stumble across it. E.g.

mv /var/www/adminer.sql.gz /var/www/$(mcookie).sql.gz


Then to get the new filename:
ls /var/www/*.sql.gz

You'll also need to ensure that the www-data user has access to the file. The easiest way to do that is transfer ownership to that user. From the commandline:

chown www-data /path/to/file.sql.gz

Hope that helps... If not, please post back and I'll respond ASAP. If you want to give me some furhter background on exactly what you're up to so I can give more specific advice, it's probably best to open a new thread (feel free to post a link to your new thread in a post here).