This blog will discuss the testing aspects of the MySQL products, testing we do for different mysql products,  how we qualify the releases, some of the approaches we use, test tools we use.

Teradata Q1 disappoints. Actian acquires ParAccel. And more.

For 451 Research clients: Acquisitive Actian adds ParAccel to its growing database portfolio bit.ly/YgeY7k

— Matt Aslett (@maslett) April 29, 2013

For 451 Research clients: Tokutek releases TokuDB database storage engine as open source bit.ly/102xsSW

— Matt Aslett (@maslett) May 1, 2013

For 451 Research clients: Codership replicates partnership success with Galera Cluster for MySQL bit.ly/15dI8Hh

— Matt Aslett (@maslett) May …

We have been using the new MEB for about a year in production. The improvements over the old InnoDB Backup are phenomenal and allow us to backup with somewhat regularity.

We are on our way with the parallel features of reading and processing. From our standpoint of an enterprise, it would be really nice if we have the ability to output to multiple devices similar to RMAN's channels.

For example, we backup to disk. If I want to backup a 1TB database, I have to have 2TB of space available (1TB for yesterday's backup, 1TB for today's backup in case we have a failure during the backup). In addition, that 2TB filesystem is going to get pounded, especially if I am using multiple readers. If we could tell MEB to use TWO 1TB filesystems, that would give us better performance as well as manageability.

Just something to think about.

News and views are an integral part of our modern daily life. When it comes to the information-hungry roles such as database professionals, such need becomes more pressing. Log Buffer is one way to keep abreast of news and views from the world of Oracle, SQL Server, and MySQL.

Oracle:

There is a significant update SLOB 2, Kevin Closson informs.

Charles Hooper is grouping Data Sets by Week Number of the Month.

Chris Antognini has shared a script that is used to demo ITL deadlocks.

As …

MySQL Enterprise Backup (MEB) was born 3 years ago as a newly branded avatar of InnoDB Hot backup. Wanted to share what has gone on so far, how we at Oracle think about

backup, the milestones that we have achieved and the road ahead. The idea for this blog came to me after looking at Mikael's latest blog. While Mikael talks about MySQL, I want to talk about MEB.

When we started with InnoDB Hot backup the first challenge was to have it adhere to the development, quality and release processes for MySQL. This meant creating a

quality plan, getting it into the development trees of MySQL and ensuring that each piece of new code went through architecture and code review. Though the initial implementer and architect of Hot backup continues to work with the MEB team, there were a host of new engineers to be trained. We also …

On a regular basis I plan to summarize the latest news from MySQL Engineering. I hope you find it useful.

April highlights were the DMR’s coming out for both MySQL Cluster 7.3.2 and MySQL Server 5.7.1. For those that have been missing the launchpad versions of those, I apologize for the delay, but they should be there now if you want to dig into the changeset details. And to repeat what I’ve said in the past, there should not be a delay between releases on launchpad and src tar balls, so please keep bugging me when you see glitches there. Personally I also very much enjoyed the April Percona conference where I met a lot of old good friends and gave a keynote. You can …

This afternoon, Arjen Lentz and I were discussing InnoDB’s behavior without a declared PRIMARY KEY, and the topic felt interesting enough and undocumented enough to warrant its own short post.

Background on InnoDB clustered keys

In The physical structure of InnoDB index pages I described how “Everything is an index in InnoDB”. This means that InnoDB must always have a “cluster key” for each table, which is normally the PRIMARY KEY. The manual has this to say in Clustered and Secondary Indexes:

If the table has no PRIMARY KEY or suitable UNIQUE index, InnoDB internally generates a hidden clustered index on a synthetic column containing row ID values. The …

A cold cache, or a poorly tuned cache can be responsible for a number of performance problems. If we look at the data and indexes of InnoDB, the cache responsible is called the InnoDB buffer pool.

In earlier versions of MySQL the default value for the setting innodb_buffer_pool_size was 8M - which is a little out of date when you consider the recommended value to be 50-80% of system memory. In MySQL 5.5 the default value was increased to 128M, which is a comprimise made for users that may install MySQL on a development machine and not have it running as a dedicated server. In production, it is unlikely that you will buy a new server with less than 64GB of RAM, so it is quite typical that this setting is 50GB+

So lets talk about the behavior of the InnoDB buffer pool -

Up until and including MySQL 5.5

When MySQL starts up, the buffer pool is completely empty. As queries are executed, MySQL will …

The MariaDB project is pleased to announce the immediate availability of the MariaDB Java Client 1.1.2. This is a Stable (GA) release. See the Release Notes and Changelog for detailed information on this release and the About the MariaDB Java Client page in the AskMonty Knowledgebase for general information about the client.

Download MariaDB Java Client 1.1.2

Release Notes …

SAP HANA , having entered the data 2.0/3.0 space at the right time, has been getting traction lately; and there will be lot of users like me who wants to[...]