With such a wide range of options available for running MySQL based servers in Amazon cloud environments, how do you choose? There’s no doubt it’s a challenge. In this two-part series of blog posts, we’ll try to draw a fair and informative comparison based on well-established benchmark scenarios – at scale.

In part one we will discuss the performance of the current Amazon RDS services – Amazon Aurora and Amazon RDS for MySQL – and compare it with the performance of Percona Server with InnoDB and RocksDB engines. And in part two we will go over costs and efficiencies to look for. All this information is necessarily number-heavy, but hopefully, you’ll enjoy the experiments!

Evaluation scenario The benchmark scripts

For these evaluations, we use the …

Please join Percona’s Service Delivery Manager Rodrigo Trindade as he presents “Troubleshooting Java Connections to MySQL” on Thursday, July 18th, 2019 at 10:00 AM PDT (UTC-7).

Register Now

This talk will explain the steps needed to make a connection from Java to MySQL work and highlight potential issues you might encounter. It will cover all components, installation, and configuration.

If you can’t attend sign up anyways we’ll send you the slides and recording afterward.

Speaker: Rodrigo Trindade
Service Delivery Manager Rodrigo has a Master in Computer Science …

We are glad to announce the 1.1.0 release of the  Percona Kubernetes Operator for Percona XtraDB Cluster.

The Percona Kubernetes Operator for Percona XtraDB Cluster automates the lifecycle and provides a consistent Percona XtraDB Cluster instance. The Operator can be used to create a Percona XtraDB Cluster, or scale an existing Cluster, and contains the necessary Kubernetes settings.

The Operator simplifies the deployment and management of the Percona XtraDB Cluster in Kubernetes-based environments. It extends the Kubernetes API with a new custom resource for deploying, configuring and managing the application through the whole life cycle.

The Operator source code is available …

Overview The Skinny

Tungsten Clustering provides high availability, disaster recovery, and a host of other benefits for MySQL / MariaDB / Percona Server databases. In this blog post we will explore some of the shell aliases I use every day to administer various Tungsten Clusters.

Shell Aliases: A Quick Review Quick and Easy

A shell alias is simply a way to create a shortcut for frequently-used command sequences.

For example, I like to shorten the command clear to cls, i.e.

shell> alias cls=clear
shell> cls

If you create an alias on the fly it will be lost when the shell exits.

To save aliases so they are available to all shell sessions, update your shell’s profile or rc script.

For example, add the below line to the bottom of …

The Percona Live Open Source Database Conference, Europe 2019 will have a one week extension of the call for papers.  Our new close date will be Monday July 22, 2019.  Any and all topics related to open source database technologies are invited.

This year’s conference takes a new approach, organizing tracks along these key business themes:

• Performance & Scalability
• Public, Private, and Hybrid Clouds & Everything In Between
• Building Large, Scalable, & Secure Database Deployments
• Hot Topics, New Features, & Trends You Should Know About
• Monitor, Manage, & Maintain Databases at Scale
• How to Reduce Costs & Complexity with Open Source Databases
• Fascinating or important talks that don’t 100% fit in the other tracks …

This is a follow-up post in the MySQL Master Replication Crash Safety series.  In the previous posts, we explored the consequences of reducing durability on masters (different data inconsistencies after an OS crash depending on replication type) and the performance boost associated with this configuration (benchmark results done on Google Cloud Platform / GCP).  The consequences are summarised in

This post is a sister post to MySQL Master Replication Crash Safety Part #5: making things faster without reducing durability.  There is no introduction or conclusion to this post, only landing sections: reading this post without its context is not not recommended. You should start with the main post and come back here for more details.

And this Part #5 of the series has many sub-parts.  So far,

In week 5 of our Benefits of SQL Diagnostic Manager for MySQL (formerly Monyog) blog series, we detail MySQL and MariaDB monitoring features with SQL Diagnostic Manager for MySQL, including real-time monitoring and monitoring MySQL error logs. If you missed it, you can read our previous post on understanding database performance trends.

Fast Startup Time to Start Monitoring

Database administrators can start monitoring MySQL and MariaDB servers in less than a single minute. The unique architecture and low-footprint of SQL Diagnostic Manager for MySQL enable database administrators to install and configure all of the components that are required for monitoring MySQL and MariaDB servers very quickly.

The fast startup time is in sharp contrast with other monitoring and advisory …

This tutorial explains the MySQL INSERT command to insert single and multiple rows in a table. Here, you’ll find some unique ways with different variations for adding records with fully working examples. 1. INSERT Statement Syntax 2. INSERT Single Row 3. INSERT Default Values 3. INSERT Date Columns 4. INSERT Multiple Rows Let’s now read and understand each of the section one by one. MySQL INSERT statement As stated initially, the INSERT command is a built-in MySQL statement which inserts the specified records into a given table. So, let’s first check the details and see how to use the INSERT

The post MySQL Insert Statement to Add Rows appeared first on Learn Programming and Software Testing.

Recently I had a customer where every single query was running in a transaction, as well as even the simplest selects. Unfortunately, this is not unique and many connectors like Java love to do that.

In their case, the Java connector changed autocommit=off for the connection itself at the beginning, and as these were permanent connections they never or almost never reconnected.

In the slow query log we could see after every select there was a commit. So why is this a problem?

Test Case

Like always, the best way to deal with a problem to test it. I have created two EC2 instances t3.xlarge with Ubuntu, one for application and one for the databases.  I have used sysbench to run my tests.

I have created a table with 1 million records and was running simple primary key point selects against the database. I was using …