Difference between revisions of "Database - MariaDB"
Line 178: | Line 178: | ||
**<code>CREATE DATABASE db_name;</code> | **<code>CREATE DATABASE db_name;</code> | ||
***You will need to grant access to any new database to the appropriate user(s). This is covered more clearly on pages where you create specific databases... | ***You will need to grant access to any new database to the appropriate user(s). This is covered more clearly on pages where you create specific databases... | ||
***<code>GRANT ALL ON db_name.* TO 'user'@'localhost';</code> | |||
***(as one example) | |||
*Trash a complete database '''(WARNING! DANGER! DAMAGE LIKELY!)''' | *Trash a complete database '''(WARNING! DANGER! DAMAGE LIKELY!)''' | ||
**<code>DROP DATABASE wp_Someblog;</code> | **<code>DROP DATABASE wp_Someblog;</code> |
Latest revision as of 14:45, 8 September 2024
11 (bullseye) 12 (bookworm) |
|
Here in the NerdMage's Lair, we have switched from mySQL to MariaDB lately. This has been prompted by the apparent abandonment of mySQL. (Yes, this IS a primarily Debian environment...)
Something to note: When working with MariaDB, you will occasionally see utilities & such referring to mySQL. This is normal as MariaDB is a replacement for mySQL & the developers have not recreated things that work for both. (in many cases, this means that commands you would expect to be based on mariadb will be mysql instead.)
Installation
sudo apt install mariadb-server mariadb-client php-mysql
Initial Configuration
sudo mysql_secure_installation
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY! In order to log into MariaDB to secure it, we'll need the current password for the root user. If you've just installed MariaDB, and haven't set the root password yet, you should just press enter here. Enter current password for root (enter for none):
Press Enter
OK, successfully used password, moving on... Setting the root password or using the unix_socket ensures that nobody can log into the MariaDB root user without the proper authorisation. You already have your root account protected, so you can safely answer 'n'. Switch to unix_socket authentication [Y/n]
Select N
... skipping. You already have your root account protected, so you can safely answer 'n'. Change the root password? [Y/n]
Select N
... skipping. By default, a MariaDB installation has an anonymous user, allowing anyone to log into MariaDB without having to have a user account created for them. This is intended only for testing, and to make the installation go a bit smoother. You should remove them before moving into a production environment. Remove anonymous users? [Y/n]
Select Y
... Success! Normally, root should only be allowed to connect from 'localhost'. This ensures that someone cannot guess at the root password from the network. Disallow root login remotely? [Y/n]
Select Y
... Success! By default, MariaDB comes with a database named 'test' that anyone can access. This is also intended only for testing, and should be removed before moving into a production environment. Remove test database and access to it? [Y/n]
Select Y
(Don't think I've EVER used the test database... EVER...)
- Dropping test database... ... Success! - Removing privileges on test database... ... Success! Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Reload privilege tables now? [Y/n]
Select Y
This is a silly question.
... Success! Cleaning up... All done! If you've completed all of the above steps, your MariaDB installation should now be secure. Thanks for using MariaDB!
Allowing non-localhost access
By default, MariaDB (like MySQL) binds to 127.0.0.1...
This is ugly, but works for now:
sudo vi /etc/mysql/mariadb.conf.d/50-server.cnf
& change
bind-address = 127.0.0.1
to
bind-address = Machine.Domain.TLD
(where Machine.Domain.TLD is the FQDN or IP address of the database server itself...)
Set up at least one database user
sudo mysql -u root
CREATE USER 'someone'@'localhost' IDENTIFIED BY 'password'; FLUSH PRIVILEGES; EXIT;
(Hint: This'd be a good time to create yourself as that user with your non-admin password of choice...)
Remotely accessed Database Server
If this is to be a remotely accessed Database Server, 'localhost' will actually be the name/address of the remote machine you'll access from.
Possibly even '%' as a wildcard.
A NOTE: If you have a user @ a specific host, then add the same user @ '%', MariaDB will not let the wildcard user have priveleges...
Some Reference Materials
- SQL Tutorial
- Commands
- Basic SQL Commands - The List of Database Queries and Statements You Should Know
- How to Manage MySQL Databases and Users from the Command Line
- Some handy tutorials
Some Useful Things
(These have yet to be fully tested on MariaDB as opposed to mySQL...)
- Sign into MySQL
sudo mysql -u root -p
- Restart MySQL
sudo systemctl restart mariadb.service
- Change a user password
ALTER USER 'userName'@'localhost' IDENTIFIED BY 'New-Password-Here';
- Create a new database
CREATE DATABASE db_name;
- You will need to grant access to any new database to the appropriate user(s). This is covered more clearly on pages where you create specific databases...
GRANT ALL ON db_name.* TO 'user'@'localhost';
- (as one example)
- Trash a complete database (WARNING! DANGER! DAMAGE LIKELY!)
DROP DATABASE wp_Someblog;
- List existing databases
SHOW databases;
- List existing users
SELECT user,host FROM mysql.user;
Move a database from one server to another
On the originating server:
sudo mysql -u root -p
GRANT ALL ON *.* TO 'user'@'localhost';
FLUSH PRIVILEGES;
EXIT;
mysqldump -u user -p DBname > DBname.sql
scp DBname.sql user@Machine.Domain.TLD:~
On the destination server:
Create the user & database (following the instructions for the application requiring the database)
mysql -u user -p DBname < DBname.sql
If using a separate DB Server...
Create the user & database on the DB Server, then log onto the application server &do the following
(You may have to backtrack & SCP the file to the application server... :P )
mysql -u user -p -h Machine.Domain.TLD DBname < DBname.sql