This is a quick blog demonstrating a couple backup Restore uses cases within a MySQL InnoDB Cluster 8.0 setup. The backup used was completed in a previous blog (part 2 in this series) with the MySQL Enterprise Backup 8.0 utility. I’ll then use that backup to build an additional member to add to the cluster. This blog… Read More »
10 Older Entries »
Features and capabilities continue to arrive in MySQL 8.0, most recently noted in the GA release of MySQL 8.0.13. The mysql-shell 8.0.12 release introduced a number of things, an important part was a cross-platform mysql-shell secure password handling facility. The MySQL Login-paths are a part of that security focus. Here we will look at where InnoDB Cluster 8.0,… Read More »
In Jesper’s blog on Persisted Variables …he introduced us to this new capability using the PERSIST and PERSIST_ONLY keywords. With new MySQL features, such as PERSIST come new areas that we need to pay attention to when doing backup and restore activities. Namely to manage the log file that the PERSIST capability uses, as it’s a… Read More »
In another post, I explained how to use the MySQL Query Re-write Plugin to manipulate data that didn’t exactly match SQL standards of MySQL. In this post, I am going to give you another example on how to use a trigger to parse non-conforming data so the data can be written to a MySQL database.
A customer came to me with a problem. They were using third-party software which produced multiple rows of comma-separated data (like a .csv file), but all of the data wasn’t on a single row. Instead, the data consisted of multiple rows of data, separated by commas and with line feeds after each row of data. Here …[Read more]
There are lots of new features in MySQL 8.0 that was recently released including our Document Store capability. There are a few core capabilities related to InnoDB Cluster in 8.0 that I’d like to share but some will arrive in some coming blogs. Primarily here I’ll point out some nice details with InnoDB Cluster 8.0… Read More »
As of MySQL 5.6.24, MySQL Enterprise Edition includes MySQL Enterprise Firewall, an application-level firewall (it runs within the mysql database process) that enables database administrators to permit or deny SQL statement execution based on matching against whitelists of accepted statement patterns. This helps harden MySQL Server against attacks such as SQL injection or attempts to exploit applications by using them outside of their legitimate query workload characteristics.
Each MySQL account registered with the firewall has its own whitelist of statement patterns (a tokenized representation of a SQL statement), enabling protection to be tailored per account. For a given account, the firewall can operate in recording or protecting mode, for training in the accepted statement …[Read more]
MySQL Package Management Options In this blog we will explore some interesting ways to install MySQL Community and Enterprise Edition binaries using your associated Linux package manager. In this case we’ll look mostly at the Yum package manager on Oracle Linux. The benefit of these package managers is that you can install software packages easily,… Read More »
The MySQL Enterprise Audit plug-in is part of the MySQL Enterprise Edition (available through a paid license). Basically, Enterprise Audit tracks everything that is happening on your MySQL server, and can be used to protect/detect the misuse of information, and to meet popular compliance regulations including HIPAA, Sarbanes-Oxley, and the PCI Data Security Standard.
MySQL Enterprise Audit uses the open MySQL Audit API to enable standard, policy-based monitoring and logging of connection and query activity executed on specific MySQL servers. Designed to meet the …[Read more]
But the real magic happens on the backend. This is the ecosystem that really powers your website. One writer has articulated this point very nicely as follows:
The technology and programming that “power” a site—what your end user doesn’t see but what makes the site run—is called the back end. Consisting of the server, the database, and the server-side applications, it’s the behind-the-scenes functionality—the brain of a site. …[Read more]
OK, Y’all. If you have been a DBA long enough you have run into situations where you’ve had to import DDL from another database instance and forgotten to remove AUTO_INCREMENT on a table definition. Sometimes this means your auto_increment is way up in the millions and you have 10 rows in the table. People worried about ID depletion on an integer column will do a “facepalm”.
Making matters worse, having perhaps done this on more than one table, sometimes it’s a real pain to detect and fix the issue of auto_increments being much higher than you want them to be across a big number of tables. Sometimes the pain is so great that you might want to simply repeat your data importation.
This quick and dirty “southern fried” script will help you report and rectify that. It detects …[Read more]
10 Older Entries »