This should sound familiar:

One of the great lies about NoSQL databases is that they’re simple. Simplicity done wrong makes things a lot harder and more complicated to develop and operate. Programmers and operations staff end up reimplementing (badly) things the database should do.

Nobody argued this line of reasoning more vigorously than when trying to defend relational databases, especially during the darkest years (ca. 2009-2010), when NoSQL still meant NO SQL DAMMIT, all sorts of NoSQL databases were sprouting, and most of them were massively overhyped. But as valid as those arguments against NoSQL’s “false economy” simplicity were and are, the arguments against relational databases’ complexity hold true, too.

The truth is that no database is really simple. Databases have a lot of functionality and behaviors—even the “simple” databases do—and require deep knowledge to use well when …

#DBHangOps 12/11/14 -- Mixing Metadata with Data, InnoDB Compression, and more!

Hello everybody!

Join in #DBHangOps this Thursday, December, 11, 2014 at 11:00am pacific (18:00 GMT), to participate in the discussion about:

• Mixing Metadata and Data (requested by Shlomi Noach)

  • E.g. schema representing some data instead of metadata

• InnoDB Compression (requested by John Cesario)

  • How did you performance tune it for MySQL 5.6?
  • Expected metrics changes when enabling it
  • Overall performance with InnoDB compression enabled vs. disabled
  • Comparing TokuDB and InnoDB compression

You can check out the event page at …

This should sound familiar:

One of the great lies about NoSQL databases is that they’re simple. Simplicity done wrong makes things a lot harder and more complicated to develop and operate. Programmers and operations staff end up reimplementing (badly) things the database should do.

Nobody argued this line of reasoning more vigorously than when trying to defend relational databases, especially during the darkest years (ca. 2009-2010), when NoSQL still meant NO SQL DAMMIT, all sorts of NoSQL databases were sprouting, and most of them were massively overhyped. But as valid as those arguments against NoSQL’s “false economy” simplicity were and are, the arguments against relational databases’ complexity hold true, too.

The truth is that no database is really simple. Databases have a lot of functionality and behaviors—even the “simple” databases do—and require deep knowledge to use well when …

Madrid MySQL Users Group will have its next meeting on Tuesday, the 18th of December. Details can be found on the group’s Meetup page here: http://www.meetup.com/Madrid-MySQL-users-group/events/219081693/.  This will be meeting number 10 of MMUG and the last meeting of the year. We plan to talk about MySQL, MariaDB and related things. An excuse to talk about our … Continue reading MMUG10: Madrid MySQL Users Group meeting to take place on 18th December 2014

MariaDB tries to encourage use of many storage engines, which Oracle doesn't bother with. The ones that could be considered -- occasionally! -- as InnoDB replacements are: Mroonga, TokuDB, and Aria.

Mroonga

I predicted that Mroonga would be in MariaDB 10.0.8, and behold, here it is in MariaDB 10.0.15. Truly I am the Nostradamus of the database world.

It's a general-purpose storage engine, in that it doesn't have serious limitations regarding what can be stored or indexed. I think its "column-store" feature has limited appeal, but as I saw in January, it's dandy for full-text searching. This time I look at the list of "Full-Text Restrictions" in the MySQL manual, and quote from it:

"Full-text searches are supported for …

Intro

I had the opportunity to work with a variety of databases: Firebird (yeap!), MySQL, Postgres, Oracle and SQL Server. And to count the NoSQL ones I was able to work with MongoDB and DynamoDB.

I have different opinions about each one of the above (note that I didn't include Access on the list, as far as I know, that is not a database). Also, it is not secret that I like Amazon AWS products, and using some of them daily I can see why each service can be magically integrated to achieve a goal. …

Do you use Google’s Go language (golang)? Do you use a relational database such as MySQL or PostgreSQL with it? Do you want to learn how to?

Go has a package called database/sql for connecting to relational databases. There’s package documentation, but you’ll need to read the source code if you really want to understand how to use the package. The documentation doesn’t really explain how to use the package, it just explains what it does.

Fortunately, there’s a free, online, opensource tutorial that fills this need. If you haven’t read it, I highly recommend it. (I am one of the authors.) There is a lot of wisdom from very experienced people in the tutorial, including the two primary authors of the main MySQL driver for Go.

The tutorial is online at go-database-sql.org.

Do you use Google’s Go language (golang)? Do you use a relational database such as MySQL or PostgreSQL with it? Do you want to learn how to?

Go has a package called database/sql for connecting to relational databases. There’s package documentation, but you’ll need to read the source code if you really want to understand how to use the package. The documentation doesn’t really explain how to use the package, it just explains what it does.

Fortunately, there’s a free, online, opensource tutorial that fills this need. If you haven’t read it, I highly recommend it. (I am one of the authors.) There is a lot of wisdom from very experienced people in the tutorial, including the two primary authors of the main MySQL driver for Go.

The tutorial is online at go-database-sql.org.

It is easy to set up a replication topology with MySQL Sandbox, and I use it for lots of testing scenarios. For example I used MySQL Sandbox to run the tests for yeterday's post about the way UUIDs are replicated in row-based replication (RBR) versus statement-based replication (SBR).

Here's how easy it is to set up a replicated sandbox for testing:

Installing MySQL Sandbox

If you've never installed MySQL Sandbox before, you can do so by running a single command as root:

sudo su - cpan MySQL::Sandbox

Download the MySQL binary

Pick the appropriate binary based on your OS and the version of MySQL you want to use. In my case I'm on Mac OS X and I want to test MySQL 5.6 so I went to …

Tweet