MySQL April Newsletter is now available! Read this edition to learn more details about the abundant product announcements we made recently, including MySQL 5.7 Development Milestone Release, MySQL Workbench 6.1 GA, as well as the Release Candidate of MySQL Fabric. You'll also find information regarding the latest white papers, upcoming webinars and events, and technical blogs for tips and tricks using MySQL.

Enjoy and hope you find it informative! 

MySQL for Visual Studio is a product including all of the Visual Studio integration previously available as part of Connector/Net. The 1.2.0 version is an alpha release of this product that intents to introduce users to the new features in this version.

I will be speaking at the Chicago MySQL Users Group meeting on May 21st at 223 South Wacker Drive. Times, subject of the talk, and other details will be flushed out later but be aware that you will have to RSVP to get you name of the security guard’s list for admission.

Chicago Pizza and MySQL 5.7

The meeting will start at 6:30PM in the Oracle office at 233 South Wacker Drive on the 45th floor. The presentation will be on MySQL 5.7.

The latest benchmarks show that MySQL 5.7 is now able to scale to 60 cores, which is quite an incredible feat when you compare to the 4-8 core scaling of MySQL 5.1 just a few years ago. These improvements are the result of a lot of heavy lifting to reorganize internal locking structures, and I have an earlier blog post on what is a mutex anyway? which may help serve as an introduction.

While I consider horizontal scaling and projects like MySQL Fabric to be very important, it should be stated that horizontal and vertical scaling are really orthogonal choices. That is to say that a given database technology should ideally support both options, …

Dynamic range access (aka “Range checked for each record” since that is what EXPLAIN will say in the ‘Extra’ column) is one of the big mysteries to MySQL users. The reason is that it is used for queries that are less common, such as queries with non-equality join predicates. The following query is an example; it finds the number of messages sent since the user was last logged in:

EXPLAIN SELECT user.user_id, COUNT(message.id)
FROM message, user
WHERE message.send_date >= user.last_activity
GROUP BY user.user_id;

However, although such join predicates are less common, it doesn’t mean that the dynamic range access method is not important.

How the dynamic range access method works

It is easier to explain dynamic range access if we consider a “normal” join first, so let’s take a look at this query with an equality join predicate:

mysql> EXPLAIN SELECT user.user_id, user.name, …

April 22, 2014 By Severalnines

Join our upcoming webinar New Features Webinar on ClusterControl 1.2.6 - May 13th 2014 with live demo. Click on following banner to register:

The Severalnines team is pleased to announce the release of ClusterControl 1.2.6. This release contains key new features along with performance improvements and bug fixes. We have outlined some of the key features below. 

Highlights of ClusterControl 1.2.6 include:

• Centralized Authentication using LDAP or Active Directory
• Role-Based Access Control 
• OpenStack: Galera Deployment Automation
• Hybrid setups with Galera and Asynchronous MySQL Replication
• Manage multiple Galera …

Madrid MySQL Users Group will have its next meeting on the 24th of April. Details can be found on the group’s Meetup page. We plan to talk about WebScaleSQL and I will give a short presentation on how to build WebScaleSQL RPMs on CentOS 6.  The meeting will be in Spanish. We’ve changed the place that … Continue reading MMUG7: Madrid MySQL Users Group meeting to take place on 24th April 2014

The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 10.0.10. This is a Beta release.

See the Release Notes and Changelog for detailed information on this release and the What is MariaDB Galera Cluster? page in the MariaDB Knowledge Base for general information about MariaDB Galera Cluster.

Download MariaDB Galera Cluster 10.0.10

…

This post talks about how we make use of Boost.Geometry in MySQL to implement reliable and efficient GIS functionality, as well as changes to the GIS features in the lab release. Now that InnoDB is the default storage engine for MySQL, our user base is rapidly transitioning to InnoDB. One capability that they have been demanding is a performant and scalable GIS implementation. Along with adding R-tree index support to InnoDB, we also decided to replace the original GIS algorithms with a more powerful, reliable, effective and efficient geometric engine.

One of our top queries updates a table called host_agent with status information from agents checking in with the APIs periodically. I was always a little surprised at how "hot" this particular query is. If you'd asked my intuition, I wouldn't have thought it would be in the top 25.

Over time, a thought occurred to me -- this table is a bit denormalized and needs to be refactored, and as we made progress towards that in small steps, its primary key was revealed to be wrong. That is, it wasn't truly the natural primary key for the table. And the hot update had to use a secondary index to search for the row it wanted to update. Hmmm, I thought, didn't I write High Performance MySQL and shouldn't I know a little bit about these things?

I could have tested things endlessly with measurements or benchmarks or something, but I love using VividCortex on our own systems. Pour me a glass of that VividChampagne, I'll …