Get a preview of the next advance in data management technology!  Continuent Tungsten 3.0 brings the power of advanced clustering and replication to offer data management needs for your entire business including MySQL high availability, disaster recovery, multi-master operation, and real-time data warehouse loading. With Continuent Tungsten you can apply the full power not just of MySQL but all

The MaxScale team have been working hard fixing bugs and improving performance. On Friday we released a update of MaxScale, the pluggable proxy for MySQL and MariaDB, I wanted to write a little about a few of those changes. I will not mention every change, there are release notes that give the list of bugs fixed in this version, but rather highlight a couple of performance related changes and describe the rationale behind them. However before I start on the two items I wanted to discuss just a quick note to say that this version introduces cmake as the means to build MaxScale. The previous Makefiles are still available in this version, but will be withdrawn in future versions as we transition to cmake for build, installation and packaging.
Connection StarvationIn one of the test scenarios that I was …

We have relocated the MySQL Connector/Python repository on GitHub to the following location:

https://github.com/mysql/mysql-connector-python

The old location will redirect to the above URL.

No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.

We have relocated the MySQL Connector/Python repository on GitHub to the following location:

https://github.com/mysql/mysql-connector-python

The old location will redirect to the above URL.

No, we have not updated the README.txt or made something special for GitHub. I personally don’t mind what is currently showing on GitHub: it is readable, and it is correct. I still hope GitHub will make it easier to show something else, like asking which document to display and as what format.

The theme for this series of posts is, and indicated in the previous post, "Try and try, again", and there will be more of this now when I start to make this work by playing with Oracle, with PL/SQL and with the restrictions of Oracle Express (which is the version I have available).

So, what we have right now is a way of "sending" SQL statements from Oracle to MariaDB, the question is when and how to send them from Oracle. The idea for this was then to use triggers on the Oracle tables to send the data to MariaDB, like this, assuming we are trying to replicate the orders table from Oracle to MariaDB:
In Oracle, and assuming that the extproc I have that created to send UDP …

Mon, 2014-09-29 13:00mriddoch

The MaxScale team have been working hard fixing bugs and improving performance. On Friday we released a update of MaxScale, the pluggable proxy for MySQL and MariaDB, I wanted to write a little about a few of those changes. I will not mention every change, there are release notes that give the list of bugs fixed in this version, but rather highlight a couple of performance related changes and describe the rationale behind them. However before I start on the two items I wanted to discuss just a quick note to say that this version introduces cmake as the means to build MaxScale. The previous Makefiles are still available in this version, but will be withdrawn in future versions as we transition to cmake for build, installation and packaging.

Connection Starvation

In one of the test scenarios that I was running I was observing an issue that manifested itself as pauses in the …

MySQL is the database of choice for most OpenStack components (Ceilometer is a notable exception). If you start with a small deployment, it will probably run like a charm. But as soon as the dataset grows, you will suddenly face several challenges. We will write a series of blog posts explaining the issues you may hit and how to overcome them.

Where is MySQL used in OpenStack?

Have a look at the logical diagram of OpenStack below (click the image for a larger view).

The diagram is a bit outdated: Neutron appears as Quantum and newer components like Heat are not pictured. But it shows that a database has to be used to store metadata or runtime information. And although …

MySQL Connector/Python v2.0 goes GA with version 2.0.1 GA. It is available for download from the MySQL Developer Zone! The previous post about 2.0 described what changed and what was added, here’s an overview:

• Incompatibilities
  • Supported Python: 2.6 and 2.7 and 3.3 and 3.4
  • Raw Cursors Return bytearray Objects
  • LOAD LOCAL DATA INFILE On by Default
• New features
  • New Cursors return dictionaries and named tuples
  • Options Files Support Added
• Packaging and support files removed
…

We are very happy to introduce a new MySQL utility named 'mysqlbinlogmove', which is used to relocate binary log files. This utility is one of two new utilities included in MySQL Utilities release-1.6.0 Alpha. The other utility is 'mysqlgrants', which is used to display the privileges (grants) of database objects.

Note: I use "binary log" to refer to both "kinds" of binary log files (binlog and relay log files) in general, and use "binlog" to refer specifically to those that are not "relay log" files.

The mysqlbinlogmove utility allows you to move binary log files to a new location taking care of correctly updating the respective index file for you. This utility can be very useful if you want to change the location to store the binlog file and you want to move all of the binary log files. It is also handy to archive older binary log files to a new location thereby saving disk space in the server's partition.
…

We are very happy to introduce a new MySQL utility named “mysqlbinlogmove“, which is used to relocate binary log files. This utility is one of two new utilities included in MySQL Utilities release-1.6.0 Alpha. The other utility is “mysqlgrants“, which is used to display the privileges (grants) of database objects.

Note: I use “binary log” to refer to both “kinds” of binary log files (binlog and relay log files) in general, and use “binlog” to refer specifically to those that are not “relay log” files.

The mysqlbinlogmove utility allows you to move binary log files to a new location taking care of correctly updating the respective index file for you. This utility can be very useful if you want to change the location to store the binlog file and you want to move all of the binary log files. It is also handy to archive older binary log files to a new location thereby saving disk …