DE

↑ ↓ select, Enter open, Esc close

Import a gzipped SQL dump into a database

destructiveMySQL and MariaDBalle
Adjust the values, the command updates live
user@server
gunzip -c /var/www/vhosts/example.com/wp_example.sql.gz | mysql -u dbuser -p wp_example

Decompresses the backup without creating an intermediate file and passes the SQL statements to the MySQL client. Dumps from mysqldump contain DROP TABLE by default, so existing tables with the same name are replaced. Import uncompressed files with mysql -u dbuser -p wp_example < file.sql.

Note: Back up the current state first. The target database must exist unless the dump contains CREATE DATABASE.

Also searched as

  • import mysql dump
  • restore database backup
  • import sql.gz file

Related one-liners

All in MySQL and MariaDB

Analyze the slow query log for the slowest queries

#mysqldumpslow -s t -t 10 /var/log/mysql/mariadb-slow.log
harmlessMySQL and MariaDB

Back up a single database consistently as gzip

$mysqldump --single-transaction --quick -u dbuser -p wp_example | gzip > /var/www/vhosts/example.com/wp_example.sql.gz
harmlessMySQL and MariaDB

Back up all databases into one gzipped file

#mysqldump --single-transaction --quick --all-databases --routines --events | gzip > /root/all-databases.sql.gz
harmlessMySQL and MariaDB

Back up each database into its own gzipped file

#for db in $(mysql -NBe 'SHOW DATABASES' | grep -Ev '^(information_schema|performance_schema|sys)$'); do mysqldump --single-transaction --quick "$db" | gzip > "/root/db-backup/$db.sql.gz"; done
harmlessMySQL and MariaDB

Check all MySQL tables for errors

#mysqlcheck --all-databases --check --silent
harmlessMySQL and MariaDB

Compare max connections with the peak so far

#mysql -e "SHOW GLOBAL STATUS LIKE 'Max_used_connections'; SHOW GLOBAL VARIABLES LIKE 'max_connections';"
harmlessMySQL and MariaDB

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.