Whatever Google intended to do with the latest update, I personally think there was some collateral damage done to sites like mysqljoin.com . Since this is only a site I created to show people how joins can be used within MySQL (for free), I never spent money to a SEO agency or something. All I did was installing a SEO Plugin for WordPress. Am I guilty of “over optimizing” now?

The site is approx. 1,5 years old and it grew slowly. The first few month nothing really happened, then people somehow started to link to us , people on stackoverflow.com started to reference us and things like that. To me, this looks really organic. However, the traffic dropped overnight from approx. 1500 unique visitors per day to approx. 300 unique visitors.

If this update works to fight again spammy sites in the organic results, I’m fine with it. Even though I have no idea why Google …

Being a data recovery specialist and having recovered countless GBs of corrupted, and/or stranded, InnoDB data in my days, I am very happy to hear about the new InnoDB Transportable Tablespaces coming in MySQL 5.6!

Back in the day, if you had a stranded .ibd file (the individual InnoDB data file with –innodb-file-per-table option), you basically had nothing (even though that file contained all of the data). This was because unless you had the original instance that that particular .ibd file (table) originated from, there was no way to load it, import, or dump from it. So it was not of much use, though all the data was *right* there.

Thus I created the method of Recovering an InnoDB table from only an .ibd file (I should note that this was before the …

Read the original article at Bulletproofing MySQL replication with checksums

Your MySQL replications running well? You might not even know if they aren’t. One of the scariest things about MySQL replication is that it can drift out of sync with the master “silently”. No errors, no warnings.

1. What and Why?

MySQL’s replication solution evolved as a statement based technology. Instead of sending actual block changes, MySQL just has to log committed transactions, and reapply those on the slave side. This affords a wonderful array of topologies and different uses, but has it’s drawbacks. The biggest occur when data does not get updated or changed in the …

Just as one does, I was finding stuff to delete and I stumbled across this old directory which had dozens of BitKeeper work directories. Of course, I don't have a valid license for BitKeeper anymore and these directories haven't been touched in years!

I guess I shall sit on them for a while.

Virtualization is important and Dave Welch from the House of Brick gave a great presentation of experiences with VMWare and Tier 1 databases. It was a comprehensive presentation, but the white paper was easier to follow. The slides were complete but the volume of information was a lot for an hour presentation. Well worth the time though.

Utah Oracle User Group (UTOUG) announced a call for Fall Symposium papers today. The Fall Symposium will be in Salt Lake City on 9/6/2012. If you’re interested in presenting on Oracle or MySQL, the call for presentations will be open until 6/15/2012.

The conference party was tonight, and it provided some nice orderves and pizza. The theme was a return to 1980s music, and …

While preparing for the yesterday's MySQL/MariaDB 5.5 talk at the Mail.Ru technical forum, I downloaded the source code of three 5.5 forks - Oracle, Percona and MariaDB. And was happy that my g'old way of sandboxing an instance without installing it still works.

I don't know whether MySQL sandbox is using this approach under the hood, here it goes:

1. Make sure /etc/mysql/my.cnf is not present or commented out.
2. Create a ~/.my.cnf with few important lines:

[client]
port        = 3307
host        = 127.0.0.1
socket      = /opt/local/var/mysql/mysql.sock

[mysqld]
gdb # this one is necessary just to sandbox
max_allowed_packet=16M
port=3307
socket=/opt/local/var/mysql/mysql.sock
language=/home/kostja/work/mariadb/5.5/sql/share/english
character-sets-dir=/home/kostja/work/mariadb/5.5/share/charsets …

Collaborate 12 is in Vegas and Collaborate 13 will be in Denver. Mark your calendars now!

The last MySQL session for this year’s Collaborate is over. There is another day of sessions to go but they will go on without MySQL-centric topics. The majority of those the MySQL Community Team have talked to are Oracle professionals looking to expand their support for existing MySQL instances in their organizations or those looking to move some aspect of their data over to MySQL. Many use Collaborate for obtaining technical information as they feel Oracle Open World is too frenzied to get niyty gritty details. Attendance at MySQL sessions were much larger than last year and demo pod booth action was heavy with those seeking specific answers to their questions. And they were seeking details on the NoSQL/SQL InnoDB/NDB interface, operational …

Following my previous benchmark of Samsung 830, today I want to show results for STEC MACH16 SATA card, 200GB size, this card is based on SLC, and regarding STEC website, it is an enterprise grade storage.

For tests I use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I switched to use async IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and second, async mode allows to see maximal possible throughput, it does not show reliable latency though, as it appears there is no a reliable way in the Linux asynchronous IO library to get time metrics for particular IO …

You might remember this little thing called the Y2K bug.  That’s twelve years ago, but MySQL still supports a YEAR(2) data type.  A recent internal discussion made me realize there were aspects of YEAR(2) that I didn’t fully understand, and prompts me to challenge readers to come up with a truly viable use case for YEAR(2) data types.

A primary reason for storing only the last two digits of years is to save on storage space, so perhaps YEAR(2) makes sense for big data or in situations where storage is constrained, right?  Well, no – the number of bytes used to store YEAR(2) data is the same as what is required when YEAR(4) is used:

mysql> SHOW CREATE TABLE y2\G
*************************** 1. row ***************************
Table: y2
Create Table: CREATE TABLE `y2` (
`y` year(2) DEFAULT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1
1 row in …

In the last few weeks I’ve been caught off guard by the number of people who’ve told me they have been evaluating Percona XtraDB Cluster (link), and even more surprised at the projects they’re considering it for. Yesterday alone I spoke to several people who have been evaluating it for large, mission-critical enterprise deployments. Some new, some to replace existing systems that use standard MySQL replication. What was interesting is that some people said they’ve been putting it through its paces for months – before we even released it as GA.