Author Andriy Lysyuk.

Introduction

Unfortunately, human mistakes are inevitable. That’s how life is. Wrong DROP DATABASE or DROP TABLE may destroy critical data on the MySQL server. Obviously, backups would help, however they’re not always available. This situation is frightening but not hopeless. In many cases it’s possible to recover almost all the data that was in the database or table.
Let’s look at how we can do it. The recovery plan depends on whether InnoDB kept all data in a single ibdata1 or each table had its own tablespace. In this post we will consider the case when innodb_file_per_table=OFF. This option assumes that all tables are stored in a common file, usually located at /var/lib/mysql/ibdata1.

One Wrong Move, And The Table’s Gone

For our scenario, we use …

MySQL 5.6 has reached its EOL in February 2021, and we recommend that you start to plan migrating to MySQL 8.0. The latest version of MySQL is supported until April 2026 and keeps your database features up to date with continuously receiving updates and fixes, especially the security patches.

The next release of ClusterControl, will no longer provide a deployment option for MySQL5.6. However, we will continue to support and provide support for MySQL5.6 users on bugs and fixes related to ClusterControl for a stipulated time. 

Here are some related MySQL 8.0 blogs:

• Monitoring & Ops Management of MySQL 8.0 with …

MySQL Database Service with HeatWave: 1100x Faster than Amazon Aurora, 400x faster than Amazon RDS, 18x faster than Amazon Redshift at ⅓ the cost.

This blog post will guide you through the MySQL HeatWave references that are available today, from live webinar, to recorded videos, blogs, and more.

Let's start with a quick definition of what is MySQL HeatWave. HeatWave is a new, in-memory query accelerator for MySQL Database Service available only in the Oracle Cloud. It can accelerate performance on large multi-TB datasets, and scale across 1,000s cores. Our benchmark results and customer feedback show that HeatWave accelerates MySQL queries by 400X and is 1/3 the cost of Amazon Redshift.

Oracle MySQL Database Service, with HeatWave, is the only service that enables database admins and app developers to run OLTP and OLAP workloads directly from their MySQL database, eliminating …

MySQL Database Service with HeatWave: 1100x Faster than Amazon Aurora, 400x faster than Amazon RDS, 18x faster than Amazon Redshift at ⅓ the cost. This blog post will guide you through the MySQL HeatWave references that are available today, from live webinar, to recorded videos, blogs, and more. Let...

ProxySQL is proud to announce the latest release of ProxySQL version 2.0.17 on the 9th of February 2021

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, or the Docker image available on our Official ProxySQL Docker Repository.  ProxySQL is freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

ProxySQL v2.0.17 is a patch release comprising of minor backward compatible changes and bug fixes. 

Be sure to try out the new ProxySQL 2.0.17 release and …

Most modern websites and applications ground on data collection, storage, and analysis. Databases take an active part in building the entire Web environment. That’s why it is crucial to ensure correct data retrieval from databases and appropriate ways of data manipulation. To modify your data properly, you will need to execute SQL queries. The current […]

The post Introduction to MySQL UPDATE Statement appeared first on Devart Blog.

 Is MySQL going invisible?  Invisible Indexes were included in MySQL 8.0 and now with version 8.0.23 we have Invisible Columns.

Indexes You Can Not See!

The value of the invisible index is that it allows you to make an index disappear from the view of the optimizer.  In the distant days before 8.0, you would often delete an index you were pretty much definitively positive nobody or no query was using.  And then you would find out that yes, not only was that index you just deleted necessary to everyone in the galaxy (but maybe you)  but it was going to take some serious clock time to rebuild that index. 

But with Invisible Indexes, you issue a command like ALTER TABLE t1 ALTER INDEX i_idx INVISIBLE; and it was removed from use.  Now you can run EXPLAIN on your queries and compare results.  And if you want that index back among the visible, ALTER TABLE t1 ALTER INDEX i_idx …

HeatWave is designed to enable customers to run analytics on data which is stored in MySQL databases without the need for ETL. This service is built on an innovative, in-memory analytics engine which is architected for scalability and performance and is optimized for Oracle Cloud Infrastructure (OCI) Gen 2 hardware. This results in a very performant solution for SQL analytics at a fraction of the cost compared to other cloud services including AWS Aurora, Redshift, Google Big Query, RDS.

The amount of acceleration an application would observe with HeatWave depends upon a number of factors like the datasize, queries, operators being used in the query, the selectivity of the predicates. For the purpose of comparing, we are considering the TPCH benchmark which has the queries well defined and the only variable is the data size and the system configuration. HeatWave is able handle all workloads with a single shape so that …

HeatWave is designed to enable customers to run analytics on data which is stored in MySQL databases without the need for ETL. This service is built on an innovative, in-memory analytics engine which is architected for scalability and performance and is optimized for Oracle Cloud Infrastructure (OCI...

This blog is about table partitioning in NDB Cluster. We will see how this feature has been enhanced from version to version. Also we will see which partitioning user should use under which scenario. Here I will assume that the user has some knowledge on NDB cluster.

Data distribution and table partitioning are usually coupled together. In NDB, when we talk about table partitioning, we mean ‘data distribution’ mainly as NDB doesn’t fully support RANGE, HASH or LIST partitioning. Most of the enhancements made to partitioning over the years are about ‘data distribution’ rather than supporting various partitioning schemes. The main goals of data distribution are:

- Balance: Avoid premature bottlenecks of memory, storage, cpu or network
- Scaling: Make use of all resources, add capacity with new resources
- Efficiency: Locality of access and minimal unnecessary data transfer

To …