There's now 2 weeks left of the Call for Papers for Percona Live MySQL Conference and Expo (Santa Clara, CA). This weekend I've been finalizing my abstracts for submission and I trust many of you are doing the same. (If nothing else, do it for the free entrance! Or because you're passionate about MySQL, yeah, that's what I meant...)

This is the main annual MySQL event, so I thought it is worth the bandwidth to use these two weeks for some discussion and brainstorming. We are the MySQL community, it's up to us to make this a great conference now! This year I'm on the program committee, so I'm looking forward to reviewing many, many great proposals. At the same time, I'm interested to hear what you, dear readers - and hopefully future conference visitors - are interested in seeing at the conference? I'll share my ideas here and you can share yours in the comments …

MySQL is continuing to be a big player in hosting and cloud companies.  Two of MySQL's great features are how light weight it is and it's speed.  This gives MySQL a lot of advantages over other database vendors.  Yet it is also a disadvantage because the other larger database vendors have more infrastructure and tooling that can impact MySQL being chosen as a long term enterprise solution.

This

When InnoDB appears hung, I know the natural reaction is to check SHOW ENGINE INNODB STATUS.

In fact, it’s the first thing I check when InnoDB tables are involved.

However, I just want to iterate how valuable SHOW FULL PROCESSLIST and/or mysqladmin debug outputs can be even when it seems mysqld is hung on on InnoDB table.

Two recent cases I’ve encountered illustrate why.

Case #1:

MySQL appeared hung on the following simple, single-row INSERT:

---TRANSACTION 0 2035648699, ACTIVE 76629 sec, process no 9047,
OS thread id 3069426592, thread declared inside InnoDB 500
mysql tables in use 1, locked 1
...
INSERT INTO test (id, parent, text) VALUES (180370, 70122, 'test table')

At least that’s what it seemed per the INNODB STATUS, but unfortunately, there wasn’t any further information to go on.

The next time it occurred, SHOW FULL PROCESSLIST was captured at the time.

…

Users of MS SQL servers may find it useful to connect to their server via Windows authentication. The login dialog disables username + password in that case, as these are not required (indeed ignored by the server). The old option "Prompt for credentials" is now mutually exclusive to the new checkbox option "Windows authentication". Makes no sense to prompt for user+pass which then are ignored by the server. The connection dialog has grown a bit in its minimum height, as now the mentioned two checkboxes need vertical space. Well, features need space.



For MySQL sessions this checkbox is disabled. Although there is a MySQL server plugin which allows Windows authentication, the difference to MS SQL is that MySQL still asks for a username - only the password can be blank in that …

Users of MS SQL servers may find it useful to connect to their server via Windows authentication. The login dialog disables username + password in that case, as these are not required (indeed ignored by the server). The old option "Prompt for credentials" is now mutually exclusive to the new checkbox option "Windows authentication". Makes no sense to prompt for user+pass which then are ignored by the server. The connection dialog has grown a bit in its minimum height, as now the mentioned two checkboxes need vertical space. Well, features need space.



For MySQL sessions this checkbox is disabled. Although there is a MySQL server plugin which allows Windows authentication, the difference to MS SQL is that MySQL still asks for a username - only the password can be blank in that …

The binary version for MySQL Cluster 7.1.17 has now been made available at http://www.mysql.com/downloads/cluster/ (GPL version) or https://support.oracle.com/ (commercial version)

A description of all of the changes (fixes) that have gone into MySQL Cluster 7.1.17 (compared to 7.1.15a) can be found by combining the summaries from the official MySQL Cluster documentation for Cluster – 7.1.16 Change log & 7.1.17 Change log.

What do cruise ship management software and data warehouses have in common?  One answer:  they both depend on intermittent data replication.   Large vessels collect data to share with a home base whenever connectivity permits.  If there is no connection, they just wait until later.  Data warehouses also do not replicate constantly.  Instead, it is often far faster to pool updates and load them in a single humongous batch using SQL COPY commands or native loaders.  Replicating updates in this way is sometimes known as batch replication.  Tungsten Replicator supports it quite easily.

To illustrate we will consider a Tungsten master/slave configuration.  (Sample setup instructions …

With the release of TokuDB v5.0 last March, we delivered a powerful and agile storage engine that broke through traditional MySQL scalability and performance barriers. As deployments of TokuDB have grown more varied, one request we have repeatedly heard from customers and prospects, especially in areas such as online advertising, social media, and clickstream analysis, is for improved performance for multi-client workloads.

Tokutek is now pleased to announce limited beta availability for TokuDB v5.2. The latest version of our flagship product offers a significant improvement over TokuDB v5.0 in multi-client scaling as well as performance gains in point queries, range queries, and trickle load speed. There are a host of other smaller changes and improvements that are detailed in our release notes (available to beta participants).

TokuDB continues to lead the field by offering:

• 20x to …

I often get asked how to set up and use SSL with MySQL, especially on Windows – I think largely because the manual step-by-step is more geared towards Linux users (though this “how-to” is valid for all – anyone can copy/paste the commands after changing the paths).

So I’ve compiled a concise, yet comprehensive, how-to that I wanted to share with everyone out there who wants to set this up quickly and efficiently.

And for those who haven’t done it, setting up SSL can often seem intimidating, so I want to dispell that myth while I’m at it, and show you how quick and easy it can be to set up SSL for MySQL.

For one, I should mention that I’m using a version where SSL is ‘available’, just ‘DISABLED’ (some versions can be compiled w/out ssl support – so those would not work):

mysql> show global …

When I started with MySQL 3.22 I would start running MySQL from early beta (if not alpha) and update MySQL the same date as release would hit the web. Since that time I matured and so did MySQL ecosystem. MySQL is powering a lot more demanding and business critical applications now than 12 years ago and it also a lot more complicated product with more things which can go wrong. I see a lot fewer customers running their systems on non GA software and a lot more customers running MySQL few major version behind the most current one – if you’re not running the most demanding or quickly changing application it well might be good enough.

Many users select rather traditional/prudent approach these days and will only start considering upgrade to next major MySQL version 6+ months after release. MySQL 5.5 is out almost a year ago and I would still estimate more people running on MySQL or Percona Server 5.1 than 5.5 Facebook also sticks with …