5 years of MySQL

People often write a blog post when they reach some nice anniversary since they joined MySQL community. Well, for those old enough it usually means when they joined MySQL AB as employee. For me this was January 2008. Because I didn't remember the month correctly, I haven't blogged anything then, but decided to save it for a better opportunity - now.

TL;DR Starting this week I will be working for 10gen, selling MongoDB to the Nordics. This blog post is really long - even then it doesn't contain the most interesting stories, I'm not sure if they can ever be published. Sorry for the length, but remember you don't need to read all at once. This is my last MySQL post so save some of it for cold winter days!

2008 - Sun acquisition

read more

I wasn’t at the MySQL Conference this year but it was very nice to follow this event from Paris.
Of course I didn’t feel the general atmosphere by visiting booths or met fabulous people.
But it was a great opportunity to offer you a live post about the conference with an external point of view.

Twitter, RSS feeds (yes Google, I still use RSS), Planet MySQL and infiltrators were my best friends during this crazy week.

I would like to summarize the major announcements and events occurs during this tenth edition.
 

Oracle at Percona Live!

 
Yes, Oracle was at Percona Live 2013 and it was for the best.
I invite you to watch this

Pivotal launches. SkySQL and Mony Program merge. And much, much more

Our report on the changes in the MySQL ecosystem is now available for 451 clients and non-clients alike at bit.ly/451mysql

— Matt Aslett (@maslett) April 25, 2013

For 451 Research clients: VMware expands Serengeti’s horizons with updated Hadoop virtualization project bit.ly/17muQFI

— Matt Aslett (@maslett) April 26, 2013

For 451 Research clients: SkySQL, Monty Program merge to support MariaDB following formation of MariaDB Foundation bit.ly/10dsdjf

Continuing on from yesterday, the biggest news that I’ve noted in the past 24 hours:

For me, the biggest news in the last 24 hours so far has been:

I’m planning my calendar and thought I’d share what talks I’d be giving in Santa Clara in a couple of weeks for the Percona Live MySQL Conference & Expo 2013 and the MySQL & Cloud Database Solutions Day 2013. Its going to be a busy April 22-26 2013.

I mentioned in a recent post (and another recent, related post) I was going to try Visual Studio 2012 Express (as opposed to VS 2010 Express) for building MySQL 5.6 and MariaDB 10.0. on Windows.

I followed the exact same steps, but MySQL 5.6.10 would not build without fatal errors in 2012 (whereas it worked fine with VS 2010). Unfortunately, the fail errors were not too descriptive, so not quite sure what to do yet to fix it. Here is a brief snippet for those interested:

...
Done Building Project "C:\...\bld\sql\udf_example.vcxproj" (default targets).
Done Building Project "C:\...\bld\ALL_BUILD.vcxproj" (default targets) -- FAILED.
Done Building Project "c:\...\bld\package.vcxproj" (default targets) -- FAILED.
...
Build FAILED.
...

"c:\mysql\mysql-5.6.10\bld\package.vcxproj" (default target)

I just wanted to take a moment and thank, notice, what ever you want to call it, but share some love with all those and all things MySQL.

I read the post Let’s Celebrate MySQL 5.6 GA! – MySQL Community Reception by Oracle by Oracle MySQL Group and it got me to thinking of how proud I am of (and proud to be a part of) the whole MySQL Ecosystem.

We *should* all celebrate MySQL 5.6 GA! I well remember the 3.22 and 3.23 days, and there were many folks before me already using MySQL!!!

I love to see how it has continued to grow, the ecosystem and all things MySQL, that is. MySQL is better than ever. MariaDB is better than ever. Percona Server is better than ever. You have great Support options with MySQL/Oracle, SkySQL/MariaDB, and Percona as well – not to mention numerous others. I

I just set up a new Windows 7 machine, and built MySQL 5.6 for the first time, so I wanted to share my steps for anyone interested.

** Prerequisites **
1. Install Microsoft Visual Studio (I installed VS 2010 Express – free)
2. Install cmake
3. Install bison (make sure no spaces in path)

** Build Instructions **

cd c:\mysql\mysql-5.6.10
mkdir bld
cd bld
cmake ..
cmake --build . --config relwithdebinfo --target package

(You don’t technically need the ‘bld’ dir, but I prefer it to keep the main dir ‘clean’. Then if you need to re-build, you can quickly just delete the whole ‘bld’

I just wanted to share my steps for building MariaDB 10.0 on Windows (10.0.1 in this case):

cd maria-10.0.1
mkdir bld
cd bld
cmake .. -G "Visual Studio 10"
cmake --build . --config relwithdebinfo --target package

That’s it! The zip file is created right there in bld/.

Hope this helps.

As the press release says: “Come have a (free) beer with Monty: SkySQL & MariaDB’s 2nd Annual MySQL & Cloud Database Solutions Day”!

“Are you planning on being in Santa Clara for Percona Live: MySQL Conference and Expo in April? If so, don’t let the learning and networking stop on Thursday!

We invite you to join SkySQL & MariaDB for our 2nd Annual MySQL® & Cloud Database Solutions Day, Friday, April 26, 2013 at the Hyatt Regency Santa Clara. This event will be taking place directly after the Percona Live event.

During this free one-day event, you will receive hands-on training and consulting on MySQL and MariaDB database solutions from the experts at SkySQL, MariaDB, and their partners.”

Speakers will include Big Data, Analytics and Cloud experts, as well as SkySQL customers and MariaDB users. Including:

Monty Widenius

I enabled the InnoDB Lock Monitor in my MariaDB 5.5 instance (using XtraDB+ as the InnoDB – which is the default in MariaDB) and noticed that while the SHOW ENGINE INNODB STATUS was being logged to the error log, it wasn’t logging the “additional” lock information – it just looked like the plain ‘ole INNODB STATUS.

Long story short, Percona added a new variable so one has better control over what gets logged:

innodb_show_verbose_locks

If off (default), then the InnoDB Lock Monitor logs the normal INNODB STATUS, and if enabled, then it logs it with the extended lock information.

They also created another variable that goes along with this one (and the InnoDB Lock Monitor), which is:

innodb_show_locks_held

This

Caution: This is just a fun post.

I was performing some testing on Windows the other day and encountered the following error in the error log:

130313  9:40:03 [ERROR] Error writing file 'G:\mysql\log.txt' (errno: 28)

Quickly, I ran “perror 28″ from the command line:

c:\>perror 28
Win32 error code 28: The printer is out of paper.

Hehe, really, Windows?!?

In fact, the drive was out of space. No more could be written to the general log, hence the error.

Fwiw, the Linux OS code 28 reports what you would expect:

OS error code  28:  No space left on device

So, if you ever run into “The printer is out of paper” error, you’ll know what to do.