MySQL Sandbox is a Perl Module for installing multiple versions of MariaDB and/or MySQL in isolation from each other. It is primarily used for easily testing different server versions.

Visitfor details on how to install and use it.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_waitpid is a utility for terminating processes. It runs on Unix-like systems, making use of the kill() system call.

From , the client is called mariadb-waitpid. It can still be accessed under its original mysql_waitpid name via a symlink.

See mariadb-waitpid for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

The EXPLAIN Analyzer was an online tool for analyzing and optionally sharing the output of both EXPLAIN and EXPLAIN EXTENDED.

Using the Analyzer

Using the analyzer is very simple.

In the mariadb client, run EXPLAIN on a query and copy the output. For example:

1. Paste the output into the and click the "Analyze Explain" button.

2. The formatted EXPLAIN is shown. You can now click on various part to get more information about them.

Some Notes:

• As you can see in the example above, you don't need to chop off the query line or the command prompt.

• To save the EXPLAIN, so you can share it, or just for future reference, click the "Save Explain for analysis and sharing" button and then click the "Analyze Explain" button. You is given a link which leads to your saved EXPLAIN. For example, the above explain can be viewed here:

• Some of the elements in the formatted EXPLAIN are clickable. Clicking on them will show pop-up help related to that element.

Clients which integrate with the Explain Analyzer

The Analyzer has an API that client programs can use to send EXPLAINs. If you are a client application developer, see the EXPLAIN Analyzer API page for details.

The following clients have support for the EXPLAIN Analyzer built in:

HeidiSQL

has a button when viewing a query that sends the query to the explain analyzer.

CC BY-SA / Gnu FDL

mysqladmin is an administration program for the mysqld daemon.

From , the client is called mariadb-admin. It can still be accessed under its original mysqladmin name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

From , the client is called mariadb-embedded. It can still be accessed under its original mysql_embedded name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

From , the client is called mariadb-secure-installation. It can still be accessed under its original mysql_secure_installation name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_find_rows reads files containing SQL statements and extracts statements that match a given regular expression or that contain or statements.

From , the client is called mariadb-find-rows. It can still be accessed under its original mysql_find_rows name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_upgrade is a tool that checks and updates your tables to the latest version.

From , the client is called mariadb-upgrade. It can still be accessed under its original mysql_upgrade name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_install_db initializes the MariaDB data directory and creates the system tables in the mysql database.

From , the client is called mariadb-install-db. It can still be accessed under its original mysql_install_db name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysqlslap is a tool for load-testing MariaDB. It allows you to emulate multiple concurrent connections, and run a set of queries multiple times.

From , the client is called mariadb-slap. It can still be accessed under its original mysqlslap name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

These days, the client is called . Previously, it was named mysqldump , and is still accessible under that old name until MariaDB 11.0 when it was removed.

_{This page is licensed: GPLv2}

From , the client is called mariadbd-safe. It can still be accessed under its original mysqld_safe name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: GPLv2}

mysql-convert-table-format converts the tables in a database to use a particular storage engine (MyISAM by default).

From , the client is called mariadb-convert-table-format. It can still be accessed under its original mysql-convert-table-format name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-convert-table-format for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_tzinfo_to_sql is a utility used to load time zones.

From , the client is called mariadb-tzinfo-to-sql. It can still be accessed under its original mysql_tzinfo_to_sql name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-tzinfo-to-sql for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysqlcheck is a tool for checking, repairing, analyzing and optimizing tables.

From , the client is called mariadb-check. It can still be accessed under its original mysqlcheck name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-check for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

Shows the structure of a MariaDB database (databases, tables, columns and indexes).

From , the client is called mariadb-show. It can still be accessed under its original mysqlshow name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-show for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_plugin is a tool for enabling or disabling plugins.

From , the client is called mariadb-plugin. It can still be accessed under its original mysql_plugin name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-plugin for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

From , the client is called mariadbd-multi. It can still be accessed under its original mysqld_multi name via a symlink in Linux, or an alternate binary in Windows.

See mariadbd-multi for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_fix_extensions converts the extensions for MyISAM (or ISAM) table files to their canonical forms.

From , the client is called mariadb-fix-extensions. It can still be accessed under its original mysql_fix_extensions name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-fix-extensions for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysqldumpslow is a tool to examine the slow query log.

From , the client is called mariadb-dumpslow. It can still be accessed under its original mysqldumpslow name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-dumpslow for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mariadb-setpermission is a Perl script that was originally written and contributed by Luuk de Boer to help add users or databases or change passwords in MariaDB.

From , the client is called mariadb-setpermission. It can still be accessed under its original mysql_setpermission name via a symlink in Linux, or an alternate binary in Windows.

See for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

mysql_zap kills processes that match a pattern. It uses the ps command and Unix signals, so it runs on Unix and Unix-like systems.

Invoke mysql_zap like this:

shell> mysql_zap [-signal] [-?Ift]

A process matches if its output line from the ps command contains the pattern. By default, mysql_zap asks for confirmation for each process. Respond y to kill the process, or q to exit mysql_zap. For any other response, mysql_zap does not attempt to kill the process.

If the -signal option is given, it specifies the name or number of the signal to send to each process. Otherwise, mysql_zap tries first with TERM (signal 15) and then with KILL (signal 9).

mysql_zap supports the following additional options:

Example

pkill as an Alternative

pkill can be used as an alternative to mysql_zap, although an important distinction between pkill and mysql_zap is that mysql_zap kills the server 'gently' first (with signal 15) and only if the server doesn't die in a limited time then tries -9.

To use pkill in the same way, one must run it twice; pkill --signal 15 mysqld ; sleep(10) ; pkill -f --signal 9 pattern

_{This page is licensed: CC BY-SA / Gnu FDL}

mysqlaccess is a tool for checking access privileges, developed by Yves Carlier.

From , the client is called mariadb-access. It can still be accessed under its original mysqlaccess name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-access for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

The online EXPLAIN Analyzer tool has an open API to allow client applications to send it EXPLAINs.

Sending EXPLAINs to the EXPLAIN Analyzer

To send an EXPLAIN to the EXPLAIN Analyzer, simply POST or GET to the following address:

Replace "EXPLAIN" with the output of the EXPLAIN command and "CLIENT" with the name of your client.

Client Banner

If you like, you can have a banner promoting your client appear at the bottom of the page. Once you've added support for the EXPLAIN Analyzer to your client application, just send a logo, the name of your client, and what you want the name and logo to link to to bryan AT montyprogram DOT com.

CC BY-SA / Gnu FDL

mysqlreport makes a friendly report of important MariaDB status values.

From , the client is called mariadb-report. It can still be accessed under its original mysqlreport name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-report for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

Description

Initially, the MySQL C API was developed to be very similar to that of the mSQL database system.

Because of this, mSQL programs often can be converted relatively easily for use with MySQL by changing the names of their C API functions.

The msql2mysql utility performs the conversion of mSQL C API function calls to their MySQL equivalents.

mysqlhotcopy uses , , and cp or scp to make a database backup.

From , the client is called mariadb-hotcopy. It can still be accessed under its original mysqlhotcopy name via a symlink in Linux, or an alternate binary in Windows.

See for details.

mysqlimport is used to load tables from text files in various formats

From , the client is called mariadb-import. It can still be accessed under its original mysqlimport name via a symlink in Linux, or an alternate binary in Windows.

See mariadb-import for details.

_{This page is licensed: CC BY-SA / Gnu FDL}

Percona XtraBackup is an open source tool for performing hot backups of MariaDB, MySQL and Percona Server databases. Percona XtraBackup can perform compressed, incremental and streaming backups. It was designed to back up tables but can also back up other .

is a fork of Percona XtraBackup designed to work with encrypted and compressed tables and other MariaDB enhancements. There are many bug fixes, such as , and some unsafe or redundant options have been removed. is the recommended backup method for MariaDB servers.

xtstat can be used to monitor all internal activity of PBXT (a storage engine that is no longer supported).

xtstat polls the INFORMATION_SCHEMA.PBXT_STATISTICS table. The poll interval can be set using the --delay option, and is 1 second by default.

For most statistics, xtstat will display the difference in values between the current and previous polls. For example, if bytes written current value is 1000, and on the previous call it was 800, then xtstat will display 200. This means that 200 bytes were written to disk in the intervening period.

Using xtstat

Invoke xtstat as follows:

For example, to poll every 10 seconds:

Note that statistic counters are never reset, even if a rollback occurs. For example, if an UPDATE statement is rolled back, xtstat will still indicate that one write statement (see stat-write below) was executed.

If MariaDB shuts down or crashes, xtstat will attempt to reconnect. xtstat can be terminated any time using the CTRL-C key cimbination.

Before PBXT has recovered, not all statistics are available. In particular, the statistics relating to PBXT background threads are not available (including the sweep and chkpnt statistics).

Command line options

xtstat options are as follows:

Connection options will also be taken from the MySQL config file if available.

Size indicators

Values displayed by xtstat are either a time in milliseconds, a value in bytes, or a counter. If these values are too large to be displayed then the value is rounded and a size indicator is added.

The following size indicators are used:

Statistics

The following is a list of the statistics displayed by xtstat. Each statistic as a two-part display name. The first part is the category and the second part is the type.

You can select categories and types for display, as you require. For example --display=read will display all read activity, --display=xact|stat will display transaction and statement activity.

Note, for diagnostics it is best to capture all statistics. The reason is because you never now where a problem might turn up, so without certain statistics you may not be able to identify the problem.

More Information

Documentation on this page is based on the on the PrimeBase website.

Paul McCullagh's presentation from the 2010 User's Conference has some usage examples:

_{This page is licensed: CC BY-SA / Gnu FDL}

Build instructions for Percona XtraBackup.

Solaris 10 (SunOS 5.10) notes:

Edit utils/build.sh and add -lrt -m64 to CFLAGS and CXXFLAGS.

Make sure that you're using GNU utils for building, including make, cmake, gcc, gawk, getopt, autotools, libtool, automake, autoconf and bazaar.

If you want to change MySQL version which to build against with edit one of the following lines:

MYSQL_51_VERSION=...

MYSQL_55_VERSION=...

PS_51_VERSION=...

PS_55_VERSION=..

When ready run one of the following depending on the MySQL version which you want to build with:

AUTO_DOWNLOAD="yes" ./utils/build.sh xtradb (build against XtraDB 5.1)

AUTO_DOWNLOAD="yes" ./utils/build.sh innodb51_builtin (build against built-in InnoDB in MySQL 5.1)

AUTO_DOWNLOAD="yes" ./utils/build.sh xtradb55 (build against XtraDB 5.5)

AUTO_DOWNLOAD="yes" ./utils/build.sh innodb55 (build against InnoDB in MySQL 5.5)

_{This page is licensed: CC BY-SA / Gnu FDL}