One of our training courses has a section covering MySQL's Memcached API, and how it works. In the discussion, there's a line that goes like this:

 "A key is similar to a primary key in a table, and a value is similar to a second column in the same table"

For someone well versed in database tables but not so much in key-value stores, that sentence might take a bit of grasping. So, let's break it down.

An Example Key/Value Store 

Imagine the table kvstore has a column key and a column value. Also imagine that we've set up the Memcached plugin in MySQL and configured it to use that table and those columns as its store. I won't get into that bit for now, but trust me, it's not that hard.

You might be familiar with statements like this:

REPLACE INTO kvstore (key, value) VALUES ('X', 'Y');
SELECT value FROM kvstore WHERE key='X';

Now imagine you want to be …

I had the pleasure to actively participate in the MySQL & Friends Devroom at FOSDEM. Met old acquaintances and made new ones. I even got the chance to speak for roughly 30 minutes... And the room was packed. On top of that I also did some "booth duty", which is the same to say that I spent sometime at the Oracle's stand (together with Sveta, Lars and Lenka), where I took the opportunity to reach out to people. It was my first time at FOSDEM, and I was much impressed by the large amount of people and by the different number of brands and open source companies represented. A big thank you to Frederic, who organized the devroom event. Since I am sure he had some help, a big thank you to everyone who helped Frederic as well. It was great to be there and discuss MySQL (replication) with a lot of different people!

Dynamic Data Masking is an emerging technology that provides real-time data masking in changing environments, typically in production databases.

GreenSQL Dynamic Data Masking enables you to mask or randomize any sensitive information stored on Microsoft SQL Server, MySQL and PostgreSQL databases.

Join our live webinar and demo where David Maman,  security industry guru and GreenSQL Co-Founder and  CTO, will explain:

• What is Real-Time Dynamic Data Masking?
• How to dramatically reduce the risk of a data breach?
• How to better comply with regulations?
• How to enforce real-time dynamic data masking?
• How to provide a security …

The latest releases of MySQL Sandbox, in addition to deal with minor bugs, have mostly been necessary because of compatibility issues in MySQL, both 5.5 and 5.6.

When I found that MySQL 5.6 has some InnoDB tables inside the 'mysql' schema, I had to change the way that the sandbox used to remove all contents (the ./clear command.)

To achieve a smooth clean up, MySQL Sandbox now performs a dump of the mysql schema, and uses that saved data to restore the schema after a complete wipeout.

Unfortunately, when 5.5.30 was released, this operation resulted in a warning, due to a behavioral change.

After a careful change, and about 1200 unit tests, the latest version of …

WordPress-on-S3 makes professional website administration as easy as pie.

OblakSoft is pleased to announce availability of the ready-to-run WordPress-on-S3 / Yapixx AMI with enhanced configuration, performance, and website administration features.  Now website owners can use Webmin and phpMyAdmin for secure website administration over the Internet, and pre-configure Cloud Storage Connection for the instance.

• System administration
• Database administration
• …

Tuesday, February 5th was an important day in the MySQL ecosystem due to the release by Oracle of the long-awaited MySQL 5.6 GA. Many MySQL users have been looking forward to this release in order to benefit from the improved performance and scalability. Features such as online operations/schema changes, NoSQL access from memcached to InnoDB, multi threaded-replication and Global Transaction ID significantly improve the competitiveness of MySQL.

read more

With data volumes and user populations growing, its no wonder that database performance is a hot topic in developer and DBA circles.  

Its also no surprise that continued performance improvements were one of the top design goals of the new MySQL 5.6 release which was declared GA on February 5th (note: GA means “Generally Available”, not “Gypsy Approved” @mysqlborat)

And the performance gains haven’t disappointed:

- Dimitri Kravtchuk’s Sysbench tests showed MySQL delivering up to 4x higher performance than the previous 5.5 release.

- Mikael Ronstrom’s testing showed up to 4x better scalability as thread counts rose to 48 and 60 …

MySQL Tech Tour: From the Web to the Cloud
March 20, 2013, Stockholm, Sweden

Are you looking to deploy MySQL-based applications either on-premise or in the cloud?
Join us to learn how you can reduce costs and improve business agility while achieving the highest levels of MySQL scalability, security and uptime.

We will help you better understand:

• Why MySQL has become the leading database in the cloud, and how it addresses the critical attributes of cloud-based deployments
• How ISVs can power their SaaS offerings with MySQL
• What are the best practices to deploy the world’s most popular open source database in public and private clouds

You will also find out:

• How you can leverage MySQL together with Hadoop and other technologies to unlock the value of Big Data, either on-premise or in the cloud …

This article is the second in a series on data fabric design and introduces the transactional data service design pattern.  The previous article in this series introduced data fabrics, which are collections of off-the-shelf DBMS servers that applications can connect to like a single server.  They are implemented from data fabric design patterns, which are reusable arrangements of DBMS servers, replication, and connectivity.  With this article we begin to look at individual design patterns in detail.

Description and Responsibilities
The transactional data service is a basic building block of data fabric architectures.  A transactional data service is a DBMS server that processes transactions submitted by applications and stores data safely.  Transactional data services have the …

Ever run into a problem where an application's Master is accepting all the writes and the master's slaves lags? Ever had this same problem yet the Slave has a raid array of very fast SSDs? You must be thinking to yourself, "I call BS, Dathan; a SSD drive can do crazy IOPS". No, it's true and the reason is that mySQL only has two threads for replication.

Thread 1 is called the IO thread and its job is to download the binary logs from the server's master into relay logs on the slave. This is rarely a bottleneck since this is typically sequential disk access. Thread 2 is called the SQL thread. It's job is to take the data which was downloaded from the IO thread and apply it. Since there is 1 thread applying the SQL and that 1 thread has to read each row before writing it (that is just how a write works), that 1 Thread just couldn't move fast enough or use enough resources by itself and lags.

Here are my findings. …