The main goal of global transaction ID is to make it easy to promote a new master and switch all slaves over to continue replication from the new master. This is currently harder than it could be, since the current replication position for a slave is specified in coordinates that are specific to the current master, and it is not trivial to translate them into the corresponding coordinates on the new master. Global transaction ID solves this by annotating each event with the global transaction id which is unique and universal across the whole replication hierarchy.

In addition, there are at least two other main goals for MariaDB global transaction ID:

1. Make it easy to setup global transaction ID, and easy to provision a new slave into an existing replication hierarchy.
2. Fully support …

It's the end of the year and, before the world ends ;-) , I feel the pressure to follow up on last year's article "2011, a great year for MySQL in Review". I'll adopt a similar format and mention things in context, covering products, marketing, momentum, etc. at a high level. I may have missed something and I hope my colleagues will contribute to the list.

I really do think it's been the best year for MySQL so far... well, at least since when I signed my contract with MySQL AB at the end of 2007. We're just at the beginning of our journey and I wish to the MySQL family, to our community and ecosystem an even better 2013!

Summary
…

I recently worked on a Rails 3.2 project that used the sweet PLupload JavaScript/Flash upload tool to upload files to the web app. To make it easier for users to upload large and/or remote files to the app, we also wanted to let them upload via SFTP. The catch was, our users didn't have SFTP accounts on our server and we didn't want to get into the business of creating and managing SFTP accounts. Enter: ProFTPD and virtual users.

ProFTPD's virtual users concept allows you to point ProFTPD at a SQL database for your user and group authentication. This means SFTP logins don't need actual system logins (although you can mix and match if you want). Naturally, this is perfect for dynamically creating and destroying SFTP accounts. …

She hired the 400+ original MySQLers … and sets out to hire the SkySQLers of tomorrow! Boel Larsen blogs about open positions & life at SkySQL - and wants you to join the fun!

Those of you who know me also know that I spent over six years working for MySQL HR (for another couple of years I stayed on with Sun).  I joined as employee thirty-something, so running HR meant that I was more or less involved with hiring all of the 400 or so employees who joined after me. I knew pretty much everyone by name.

read more

In my ongoing efforts to migrate my fun side projects and coding experiments from SVN to Git I’ve come across some of my favorite Python based apps – which are all available in their respective repos on BitBucket, as follows:

IRC Bot Commander

• What it does: it’s an IRC bot that takes commands and does your bidding on whichever remote server the bot is installed on.
• How it does it: the bot runs on whatever server you install it on, then it connects to the IRC server and channel you configured it to connect to and it waits for you to give it commands, then it execs the commands and returns the output to your IRC chat window.

MacroBase – MySQL Analytics

…

As this topic came up a few times this week for discussion at various places, I thought of composing a post on “Data Scientist vs. Data Analytics Engineer”; even though[...]

2nd release of SkySQL™ Cloud Data Suite provides users with customisation capabilities for free cloud database deployments Update release: SkySQL™ Cloud Data Suite

SkySQL™ Cloud Data Suite is a collection of software components that provides a highly available database solution in a cloud environment based on MariaDB and 100% compatible with the MySQL database. It includes the following features:

• An automatic configurator
• An administrative console with ...
  • A graphical backup and recovery manager
  • The ability to deploy each instance securely within the user’s environment
  • Feature-rich, web-based query tools
  • An advanced monitoring tool
• A full set of HA solutions (synchronous and asynchronous)

…

Apart from my consulting as part of ScaleIn, I also invest to bootstrap companies with really disruptive ideas; and in the process met few database specific companies who are already[...]

Here is the typical “Big” data architecture, that covers most components involved in the data pipeline. More or less, we have the same architecture in production in number of places[...]

I was tired to get manually disk space used for all MySQL databases, I just created a stored procedure to get an overview of the database sizes in our MySQL server.

MySQL don’t have a command that allows us an overall summary of the databases, something like SHOW TABLE STATUS for databases. The “SHOW DATABASES” command lists only the current databases without any other information like how many space are using or how many tables there are, etc.

The procedure that I wrote this based on INFORMATION_SCHEMA database, which contains rich information of all existing databases.

I suggest, in a previous post, place all these procedures in a database called tools, but you can still choose different location.

So when call the procedure will have a global view of information that will be useful for maintenance tasks.

mysql> call tools.sp_overview(); …