The binary and source versions of MySQL Cluster 7.3.3 have now been made available at http://www.mysql.com/downloads/cluster/.

A description of all of the changes (fixes) that have gone into MySQL Cluster 7.3.3 (compared to 7.3.2) is available from the 7.3.3 Change log.

The binary version for MySQL Cluster 7.2.14 has now been made available at http://www.mysql.com/downloads/cluster/.

A description of all of the changes (fixes) that have gone into MySQL Cluster 7.2.14 (compared to 7.2.13) is available from the 7.2.14 Change log.

The binary and source versions of MySQL Cluster 7.1.29 have now been made available at http://www.mysql.com/downloads/cluster/.

A description of all of the changes (fixes) that have gone into MySQL Cluster 7.1.29 (compared to 7.1.28) is available from the 7.1.29 Change log.

This week we discuss MySQL's Migration Toolkit. Ear Candy is about the replication format as it propagates through multi-tier master and slaves; At the Movies is Distributed Data Analysis with Hadoop and R.

MySQL Migration Toolkit
Episode 161 where we talked about how MySQL Workbench is a replacement for the older MySQL GUI Tools, including the MySQL Migration Toolkit.

New Migration Toolkit in MySQL Workbench.
Installing ODBC Drivers for use with the Migration Toolkit.

read more

Since MariaDB aims to be a compatible/drop-in replacement to MySQL, its crucial that in 10.0 we support all the 5.6 options/system variables, else we have to clearly document them in the Knowledgebase article MariaDB versus MySQL – Compatibility.

To this extent, Sergey Vojtovich (svoj) has created MDEV-5277 as a tracker. There is also plenty of discussion on this topic at the maria-developers mailing list. I encourage current users of MySQL 5.6 to take a look at the list and comment either in Jira or on the mailing list to ensure that when …

Connector/NET 6.7 provides replication & load balancing configuration that allows to connect to master/slaves environments and at the same time balancing the request over all the available server in this scenario. This post will show you how to configure and use these new features on a console application.

DBTA roundtable: Building a Geo-Distributed Database for Your Global Applications

THURSDAY, DECEMBER 5, 2013

11:00am PT / 2:00pm ET

In today's global economy, more and more businesses have employees,

Binding threads to CPUs in the MySQL Cluster data nodes can have great benefits. So what about hyperthreading, should we use all CPU threads, or only 1 CPU thread per CPU core? The recommendation differs actually. For the most part it is beneficial to use hyperthreading. In most thread types it gives about 40% higher performance with 2 CPUs using hyperthreading compared to 1 CPU not using hyperthreading. There are a few cases where it might be beneficial to not use hyperthreading though.

The first example is for LDM threads. Using hyperthreading means we will increase the number of partitions of a table by a factor of two. In many cases this isn't beneficial, particularly when the number of LDM threads is high. I tried with using 24 LDM threads with hyperthreading on 12 CPU cores and compared it to 12 LDM threads on 12 CPU cores. This case didn't benefit from using hyperthreading of LDM threads. However if the number of LDM threads …

Thank you to the Drupal User Group Toronto for hosting me last night. My slides are now available online:

In response to some discussions:

• There is a new ‘tree-like’ EXPLAIN format in MySQL 5.6 called FORMAT=JSON. You can see an example in this post.
• innodb_buffer_pool_size is the in memory setting for how much of your data+indexes can be in RAM, and defaults to 128MB (far too small for most production environments). innodb_flush_method=O_DIRECT is the option to disable filesystem caching. Both are mentioned in my what to tune after installation guide.

Thanks …

(No, this is not a duplicate of the previous blog post I wrote. It's for another position!)

As MySQL is thriving and growing, we're looking for an experienced technical writer located in the UK or Ireland to join the MySQL documentation team.

For this job, we need the best and most dedicated people around. You will be part of a geographically distributed documentation team responsible for the technical documentation of all MySQL products. Team members are expected to work independently, requiring discipline and excellent time-management skills as well as the technical facilities and experience to communicate across the Internet.

Candidates should be prepared to work intensively with our engineers and support personnel. The overall team is highly distributed across different geographies and time zones. Our source format is DocBook XML. We're not just writing documentation, but also handling …