Book Image

MySQL 8 Cookbook

By : Karthik Appigatla
Book Image

MySQL 8 Cookbook

By: Karthik Appigatla

Overview of this book

MySQL is one of the most popular and widely used relational databases in the World today. The recently released MySQL 8 version promises to be better and more efficient than ever before. This book contains everything you need to know to be the go-to person in your organization when it comes to MySQL. Starting with a quick installation and configuration of your MySQL instance, the book quickly jumps into the querying aspects of MySQL. It shows you the newest improvements in MySQL 8 and gives you hands-on experience in managing high-transaction and real-time datasets. If you've already worked with MySQL before and are looking to migrate your application to MySQL 8, this book will also show you how to do that. The book also contains recipes on efficient MySQL administration, with tips on effective user management, data recovery, security, database monitoring, performance tuning, troubleshooting, and more. With quick solutions to common and not-so-common problems you might encounter while working with MySQL 8, the book contains practical tips and tricks to give you the edge over others in designing, developing, and administering your database effectively.
Table of Contents (20 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Copying file-per-table tablespaces to another instance


Copying the tablespace file (the .ibd file) is the fastest way of moving data around, rather than exporting and importing through mysqldump or mydumper. The data is available immediately rather than having to be reinserted and the indexes rebuilt. There are many reasons why you might copy an InnoDB file-per-table tablespace to a different instance:

  • To run reports without putting extra load on a production server
  • To set up identical data for a table on a new slave server
  • To restore a backed-up version of a table or partition after a problem or mistake
  • To have busy tables on an SSD device, or large tables on a high-capacity HDD device

How to do it...

The outline is: you create the table on the destination with the same table definition and execute the DISCARD TABLESPACE command on the destination. Execute FLUSH TABLES FOR EXPORT on the source, which ensures that changes to the named table have been flushed to disk, and so a binary table copy...