Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

MySQL (*)

How do I get a MySQL process?

Ok, I have a MySQL process. How do I create a database?

What is the DSN (hostname) I should use to connect to my MySQL database?

What is the difference between a MySQL process and a MySQL database?

If I lose my MySQL admin user password, can you help me get it back?

How do I access my MySQL database process from the ssh server command line?

Can I use ssh port forwarding to access my MySQL database from a remote location?

Where can I find more information on properly creating MySQL users?

What are the default databases present in my MySQL process?

Why do I have to pay for a stopped MySQL process?

When I change my member password, do my MySQL passwords change too?

Why do I get an error "Cannot log in to the MySQL server" when I try to log in to phpMyAdmin?

What does the MySQL Error Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) mean? (or socket 'please_see_the_faq')

When I try to log in to phpMyAdmin I get the error "the username was not provided." What should I do?

Why shouldn't I use my MySQL admin username from my web site?

What 'Host' value should I use when creating MySQL users?

How can I remove my MySQL process?

How do I enable or disable InnoDB for my MySQL process?

How can I make automatic backups of MySQL?

What username and password do I use to administer my MySQL process?

What does it mean that my MySQL process is "damaged?"

How do I upgrade from MariaDB 5.3 to MariaDB 10.x?

There is no in-place upgrade between MariaDB major versions; it is too risky and too irreversible. To upgrade, create a new process and migrate your data from the old process to the new process. This approach removes the risk of an upgrade failure, and ensures you can "roll back" and continue uninterrupted if the upgrade fails.

The recommended way to migrate data is from the ssh command line, but it can also be done via phpMyAdmin if you prefer. To do this from the command line, export the data from the old MySQL process:

YourPrompt> mysqldump --user=exampleuser --host=exampleold.db -p --lock-all-tables --databases exampledb1 exampledb2 exampledb3 >migrate.sql

(Replace exampledb1 through exampledb3 with the names of all of your databases in the process. Do not include "mysql" or "information_schema" in the list.)

Load your data into the new process:

YourPrompt> mysql --user=exampleuser --host=examplenew.db -p <migrate.sql

(Replace exampleuser with your MySQL administrator username. Both mysqldump and mysql will prompt you for the password on the next line.)

After the data is copied over, you can perform any checks or updates you wish, like updating table types to take advantage of new features. You'll also need to create users in the new process for your web site(s). (What a great time to change/upgrade the passwords!)

When you are ready, update your site(s) to use the new hostname (and, hopefully, password). Save the old values so that if something doesn't work, you can switch it back.

Once you have confirmed that everything is working as you expect, delete the old process. You may want to put this off for a week or so to see if you missed anything, but make a note to do it so you don't keep paying for the old process indefinitely.

Why do newly-created MySQL processes seem so expensive?

How do I enable or disable MySQL logs?