Book Image

The MySQL Workshop

By : Thomas Pettit, Scott Cosentino
5 (1)
Book Image

The MySQL Workshop

5 (1)
By: Thomas Pettit, Scott Cosentino

Overview of this book

Do you want to learn how to create and maintain databases effectively? Are you looking for simple answers to basic MySQL questions as well as straightforward examples that you can use at work? If so, this workshop is the right choice for you. Designed to build your confidence through hands-on practice, this book uses a simple approach that focuses on the practical, so you can get straight down to business without having to wade through pages and pages of dull, dry theory. As you work through bite-sized exercises and activities, you'll learn how to use different MySQL tools to create a database and manage the data within it. You'll see how to transfer data between a MySQL database and other sources, and use real-world datasets to gain valuable experience of manipulating and gaining insights from data. As you progress, you'll discover how to protect your database by managing user permissions and performing logical backups and restores. If you've already tried to teach yourself SQL, but haven't been able to make the leap from understanding simple queries to working on live projects with a real database management system, The MySQL Workshop will get you on the right track. By the end of this MySQL book, you'll have the knowledge, skills, and confidence to advance your career and tackle your own ambitious projects with MySQL.
Table of Contents (22 chapters)
1
Section 1: Creating Your Database
6
Section 2: Managing Your Database
11
Section 3: Querying Your Database
16
Section 4: Protecting Your Database

Types of restore

There are multiple reasons why you might want to do a restore. The most obvious one is if you lost your data – for example, after accidentally deleting the wrong data or after a hardware failure. Many of the restores you do should be to test your backups, backup procedures, and restore procedures. This means you restore the data on a temporary location and then check whether the restore is working properly and if all the data you expect to be there is there. And then there are restores you do to set up a new server. The new server can then be configured to replicate from your main server, allowing you to test a new version of MySQL before upgrading. It can also be used to test an upgrade procedure for the software you are using before doing it on the actual production instance.

The simplest restore type is to just restore everything. This is a full restore. This is what you would use if you lost all your data.

Another option is to restore a single table...