Let us check the contents of backup_educba database Sudo mysql -u root -p < backupOfEducba.sql The restoration can be done by using the following command: Now, we will restore the educba database from the backup file backupOfEducba.sql that we created by dumping the educba database previously. We can see that the educba database does not exist in our database server of MySQL. Let us now drop the database educba using the following command –Īnd now confirm the available databases by using the command – This is the dumped flat-file created after dumping the educba file that contains the command of create a database, create a table and insert queries to insert the records in the table. After opening the file, we will see that it contains all the commands of SQL that will recreate the educba database in case if we restore this file to a certain database. After, a file named backupOfEducba.sql file will be created on the same path. Note that we will have to exit from the MySQL command shell and then execute the above command. Mysqldump -u root -p -databases educba > backupOfEducba.sql Now, let us export the educba database using mysqldump command – Let us now see all the records present in developers table. Now, we will use educba database and check the tables present in it. Let us consider one example, we will firstly query on my database server to display all databases – The output can be exported to file using the following command –Īnd the temp file when opened on an editor looks like following: That gives the following output displaying all the options and usage of the same:Īs the list is too big, you can export it tho the file and then open the file to view the options and search for options that can be used in your context and use case. To see a complete list of the options that are available and can be used, we can execute the following command –
They are categorized into the following types – There are many different types of options that can be specified.
#Scriptcase chart value no decimal password
Many options we can use to specify the behavior or values of some of the objects like -u for the username using which we will login -p to mention the password and other options related to defining the behavior of dumping. Mysqldump -all-databases > nameOfBackupFile.sql Syntax of dumping complete mysql server are: > nameOfBackupFile.sql Dumping Complete MySql Server Mysqldump name_of_database > nameOfBackupFile.sqlĭumping one or more of the selected databases: However, the syntax for each of them differs and is mentioned below –ĭumping one or more of the selected tables: All three functionalities can be used by using the mysqldump command. We can create the backup by dumping one or more of the selected tables or by dumping a set of one or more databases or we can dump the entire MySQL server that will contain all databases and tables in it along with other objects. This ALTER command may result in the database collation changes and hence it is required to have ALTER privilege.
The ALTER statements may be present in the dumped file sometimes when stored programs are dumped for encoded character preservations. Similarly, while reloading or restoring the dumped data, we must possess the privilege such as CREATE, INSERT, and ALTER privilege that might be present in your dumped flat file that will be executed. If we are backing up the database that contains tables then you should have select privilege, for views it is necessary to have SHOW VIEW privilege, for triggers TRIGGER privilege and if we use –single-transaction option while dumping the database then LOCK TABLES privilege should be there with us.
It depends on the content that we are backing up. There are certain privileges on the tables, views, triggers, and transactions that we should have to use the mysqldump utility. Hadoop, Data Science, Statistics & others Pre-requisites
0 kommentar(er)
