Updated June 3, 2023
Introduction to MariaDB export database
MariaDB provides the export database functionality to the user; export database is a very good skill when a user handles the website or blog. When a database is corrupted or we need to migrate to a different server or development environment, we can use the export database concept to achieve our desired goal. In another situation, we also use the export database command when the user needs to restore the database. To perform export database commands we must have the root access to the database server and it is suitable to run the different commands. The export database commands are interchangeable. This is the best utility to use a backup copy of the server’s database using mysqldump power.
mysqldump -u specified user name –p specified database name > data-dump.sql
In the above syntax, we use the mysqldump command to export the database here, specified user name means user name that refers to the database. After that, we use the specified database name for the name of the database that we need to export, and the last part of syntax contains the data-dump.sql is the file name, it will be generated along with all the database information. This command does not generate any visual output, so first, we need to verify whether the generated copy is correct.
How to export a database in MariaDB using various ways?
Let’s see how we can export databases in MariaDB as follows.
We can perform a backup by using two methods, as follows.
1. By using Logical Export
In logical Export, we can restore data on the other hardware configuration, such as DBMS or MariaDB version. The Logical export is more flexible. We can perform logical export at the table and database level for flexibility reasons. The logical export size is larger than the physical export and takes more time to back and restore the database. The log files and configuration files we cannot consider for logical export.
2. By using Physical Export
We cannot restore data in physical export on other hardware configurations like DBMS or different MariaDB versions. We can perform physical export at the level of directories and files.
In a logical export database, we use the mysqldump command, this is more suitable, or we can say that more flexible way to perform logical export, and it is suitable for small databases. If the database size is large, it also requires a large table export time. The mysqldump exports data into the sql format and the data into the other format, such as CSV or XML format, and can be easily imported into the other database. We can also dump the data into the other version of MariaDB, MySQL, and other DBMS.
Logical Export of InnoDB
InnoDB uses the buffer pool concept to store data and index its table in the memory. When we consider performance, the buffer is very important for that purpose. The buffer contains the frequently accessed data from the MariaDB server. When we perform a full table scan at that time, it copies all data into the buffer pool, but this is the disadvantage of logical export because every time it scans the entire table or database, it is a time consuming process, so how we can avoid this problem by using the innidb_old_blocks_time system variable. It works with milliseconds, meaning recently accessed data is inserted into the new sub list of the buffer pool, and data accessed only ounces should remain in the old sub list of the buffer pool.
Now let’s see the different examples of export databases in MariaDB as follows.
First, we need to find out the path of the MariaDB server on the user machine, which means the location of the bin folder in the user machine.
Here the path of the user machine looks as follows.
C:\Program Files (x86)\MariaDB 10.5\bin
In the above path, C is the user systems drive, and the program files folder is used to store all installed software in the user machine; here, we installed MariaDB 10.5 server in which we have a bin folder as shown in the above path.
After that, we must create a new user machine folder.
Now see the actual statement of the export database as follows.
mysqldump –h 127.0.0.1 root –p sample> D:\back\demo1.sql
In the above example, we use the mysqldump command to export the database, in this example, we have a sample database, and we need to export them using the mysqldump command. In the above example, we used a local host IP address; this is a by default address of the local host, as shown in the above statement. After that, we use the root user credential to fetch the sample database. Here D is the system drive, and we created a new folder on D drive, name of the folder is back, and demo1.sql is the export database file name. In this example, we exported the database name as a sample. We illustrate the end output of the above query using the following snapshot.
Now see another way to export the database in MariaDB as follows.
mysqldump sample > samplebackup.sql
In the above example, we use mysqldump command to export the entire database. Here the sample is a database name that we need to export, and samplebackup.sql is sql filename for the export of the sample database. See here, we export only a single database, as shown in the above statement. We illustrate the end output of the above query using the following snapshot.
The mysqldump provides different options to the user as follows.
- –all- database
The above option is used to dump the entire database from the MariaDB server.
With the help of the above option, we can dump all table spaces.
We hope from this article, you have understood the MariaDB export database. We have learned the basic syntax of export databases from this article and also see different examples of export databases. This article taught us how and when to use MariaDB export databases.
We hope that this EDUCBA information on the “MariaDB export database” was beneficial to you. You can view EDUCBA’s recommended articles for more information.