Fri, 2013-11-08 09:17webmaster

There has been a lot of discussion about MariaDB 10.0 throughout the whole year. When will it be released, what will it include, what is the focus on MariaDB going forward, etc? My feeling is that people have in the past few months started to understand the value of MariaDB 10.0. There is a good group of people and companies that have been trying out and using the MariaDB 10.0 alpha releases and providing us with excellent feedback.

MariaDB 10.0 is a massive release with loads of new features which ease several pain points that MariaDB and MySQL users have run into over the years.

The highlights of MariaDB 10.0 can be divided into the following areas...

Read full blog on MariaDB.org

Last year’s AWS re: Invent conference was described by many as one of the best technology conferences of 2012. This year, we’re pleased to be a sponsor and exhibitor at the event and will be heading over to Las Vegas from November 12-15.

Visit us at AWS re: Invent, booth #1205, and meet with the GenieDB team. We will be demonstrating our new globally distributed MySQL-as-a-Service, GenieDB’s scalable, DBaaS, which allows organizations of any size to build web-scale applications that gain the benefits of geographic database distribution. GenieDB offers continuous availability during regional cloud outages and better application response times for globally distributed users. 

“Unlike many other database solutions, GenieDB enables developers to meet the challenges of cloud environments without having to give up critical database …

MySQL introduced row-based replication in version 5.1, but I still use statement-based replication most of the time. One thing I like about statement-based replication is that I can delete a row from the master that doesn't exist on the replica, without an error. I'm sure many people don't care about this feature because their master(s) and replica(s) contain exactly the same data set (maybe they even keep them in sync use pt-table-checksum and pt-table-sync). That being said, personally I have several use cases for storing different rows in the master than the replica. Here's one of them.

Recently I've been working on a project that requires deleting a …

Dear MySQL users,

The MySQL developer tools team at Oracle is excited to announce the availability of MySQL Workbench 6.0.8.

MySQL Workbench 6.0 is the new version the GUI Development and Administration tool for MySQL. This maintenance release contains over 50 bug fixes since version 6.0.7

Improvements in MySQL Workbench 6.0:

• a new redesigned Home screen
• the SQL Editor and Server Administration UIs were merged into a single connection specific interface, allowing for quick access to administration features while simplifying the location of specific features
• improved model Synchronization, lets you compare and update your EER model or database with ALTER scripts and properly handle corner cases involving objects renamed externally or sync schemas with different names
• improved support for model printing to PDF files

• all …

There has been a lot of discussion about MariaDB 10.0 throughout the whole year. When will it be released, what will it include, what is the focus on MariaDB going forward, etc? My feeling is that people have in the past few months started to understand the value of MariaDB 10.0. There is a good group of people and companies that have been trying out and using the MariaDB 10.0 alpha releases and providing us with excellent feedback.

MariaDB 10.0 is a massive release with loads of new features which ease several pain points that MariaDB and MySQL users have run into over the years.

The highlights of MariaDB 10.0 can be divided into the following areas:

• Replication enhancements
• Storage engines
• Optimizer enhancements
• Administration improvements
• Other important new features
• Merged features and functionality from MySQL 5.6

I’ll go through …

Percona Server has implemented per-query variable statement support in version 5.6.14-62.0. This feature provides the ability to set variable values only for a certain query, after execution of which the previous values will be restored. Per-query variable values can be set up with the following command:

mysql> SET STATEMENT <variable=value> FOR <statement>;

Example:

If we want to increase the sort_buffer_size value just for one specific sort query we can do it like this:

mysql> SET STATEMENT sort_buffer_size=100000 FOR SELECT name FROM name ORDER BY name;

Using the per-query variable statements with …

Recently a client asked me how long it would take for an ALTER TABLE to complete. Generally the answer is “it depends”. While this was running on a production system I tried with the Performance Schema in MySQL 5.6 to work out some answer to this question. While I never got to investigate various tests using INPLACE and COPY for comparison, Morgan Tocker made the request for experiences with online ALTER in A closer look at Online DDL in MySQL 5.6. Hopefully somebody with more time can expand on my preliminary observations.

Using Mark Leith’s ps_helper (older version) I monitored the File I/O to see if I could determine when using innodb_file_per_table the percentage of table writing to be completed.

Other data access on this slave server was disabled, …

Part of an article originally published in the article MySQL Forks: Which one is right for me?, published in the June edition of php[architect]. The preceding portion of the article is available: A Brief History of MySQL Oracle is the “official” distributor of MySQL .  MySQL AB had a policy of requiring outside code contributors [...]

In case you missed it, MySQL 5.6 added support for explicit partition selection. Since its release in MySQL 5.1, I have found partitioning an incredibly useful feature for aging out time-series data, and I plan to put this new syntax to work.

Today I wanted to show two hypothetical examples of how it can be used.

Consider it an optimizer hint

MySQL is usually able to optimize a query to search only the partitions which will be required. For example here we can see there are 4 partitions but 2 are searched:

CREATE TABLE t1 (
 id INT NOT NULL PRIMARY KEY auto_increment,
 cola char(255)
)
PARTITION BY RANGE(id) (
 PARTITION p0 VALUES LESS THAN (64),
 PARTITION p1 VALUES LESS THAN (128),
 PARTITION p2 VALUES LESS THAN (192),
 PARTITION p3 VALUES LESS THAN MAXVALUE
);

EXPLAIN PARTITIONS SELECT * FROM t1 WHERE id BETWEEN 120 …

Thu, 2013-11-07 10:43robertsilen

This past summer, when I joined SkySQL’s development team as product manager for MariaDB Enterprise, it became clear to me that the product needed to solve a specific, defined problem for customers trying to use MariaDB for business critical applications. Something that could be easily implemented, but that would remove a significant pain point. The feature we have chosen to highlight with this first release of MariaDB Enterprise is the ability to easily provision and manage nodes in a MariaDB Galera cluster using either a GUI interface or an API. Galera is powerful stuff but it is also finicky. What if we could make it so easy to set up a new Galera-based high availability cluster that people who’ve had trouble setting it up and evaluating it manually could just click a few buttons and provision and bring up a working high availability database cluster?

Interesting, but not enough. What if the …