We were using replication to deal with certain queries that were producing table scans. I realize this is not a great long term solution but we were migrating a web site that was set up this way, so it wasn’t really a choice.

We had a database that was a mix of InnoDB and a few MyISAM tables. The MyISAM tables were used for fulltext searches.

To get a database dump, we were using the command
mysqldump --all-databases --single-transaction --master-data=1 > dumpfile.sql

We’d then import the dump into a DB slave. When we’d bring a slave up and reply the log, we’d get a duplicate key error. After a few times, we noticed it was always on the MyISAM table. This is because MyISAM does not use transactions, and –single-transaction does not place a read lock on tables. Data can be inserted into the table during the backup but before that table is dumped.

In conclusion, if you’re using …

Appcelerator introduces new open source RIA platform. Corratech launches open source integration project. Study looks at Asterisk usage in the enterprise. (and more)

Hakano Changes Name to Appcelerator; Launches Open Source RIA Platform Company, Appcelerator (Press Release)

Corratech launches OPENSUITE, an open source integration project, CorraTech (Press Release)

Asterisk takes hold in the enterprise, PIKA study shows, PIKA Technologies (Press Release)

…

I just stumbled upon an excellent article where Marten Mickos (CEO of MySQL) gives some tips about how to become a disruptor in the software industry. Here is a short summary, though, as always, I recommend reading the whole interview.

• Follow no model: At MySQL, [...] we took our cues from other industries
  

Solid has released solidDB for MySQL 5.0.45-0079. New features include support for creating foreign keys that reference nullable UNIQUE KEYs and support for enabling and disabling indexes (greatly improves mysqlimport restore times). There are also a significant number of bug fixes. For the full detailed list of bug fixes and enhancements, please see the ChangeLog. The download is at http://dev.soliddb.com/download

The fifth and last abstract submitted for the O’Reilly MySQL Conference in April 2008.

As an independent consultant, there are quite a few trouble spots I see repeatedly. I’ll discuss five of them, and how to avoid them in your own infrastructure.

As an independent consultant for twelve years, I?ve encountered a lot of interesting and challenging projects. I?ll discuss five different cases, and what lessons I took away from each.

1. Intro
2. The Right Hardware
3. Importance of Good Testing
4. Patchwork or Good Design
5. Don?t Mix Opposites
6. Use The Technology
7. Conclusion

The fourth in a series of five abstracts for the O’Reilly MySQL Conference in April 2008.

Learn how to audit your systems, and run through the right checklists so you can sleep better at night knowing your systems are more secure.

Security is on everyone?s radar these days. You may be wondering yourself whether your database systems are really as secure as they should be. We?ll discuss some of the latest vulnerabilities, and what you can do to protect your systems.

1. Introduction
2. Authentication
3. SQL Injection
4. OS Security
5. Network Security
6. Conclusions

This is the third in a series of five abstracts submitted to the O’Reilly MySQL Conference in April 2008.

MySQL has a great facility for creating a read-only failover database. We’ll show you how to setup, start, failover, and monitor it.

Setting up MySQL to have a master + slave failover capability might be intimidating, but it needn’t be.

1. Intro
2. Anatomy of MySQL Replication
3. Initial Master copy
4. Setup + starting the slave
5. Failover from Master
6. Adding another slave
7. Monitoring your slave db
8. Conclusions

The second in a series of five abstracts for the O’Reilly MySQL Conference in April 2008.

Inevitably hackers are trying to get at your data, so you mine as well know what they can and can’t do. What better way to discover where you’re vulnerable than hacking your own systems.

Operating Systems have bugs, Database Software has bugs, and so does your application, probably. A better question is how hackable are you? We?ll look at some of the nefarious ways intruders can get in, so you?ll better know how secure your systems really are.

1. Intro
2. OS level
3. Database level
4. Application level
5. Conclusions

According to my findings in Bug #31876, MySQL does not commit data to disk in Windows using the same method MS SQL Server and DB/2 are using. The method MySQL uses appears to be seven times slower in pathological scenarios.

The bug report contains a patch - thanks to the MySQL WTF (The Windows Task Force) and the lab provided by the customer for helping me to find that.

Does this work for you? I want to hear about your test results.

Since few days ago I had no problem to perform my data backups using mysqlhotcopy.
Tonight I had an astonishing problem:

Invalid db.table name 'archivio.archivio`.`almanacco' at /usr/bin/mysqlhotcopy line 859
Invalid db.table name 'banner.banner`.`adv' at /usr/bin/mysqlhotcopy line 859

… and so on … for every database to backup.

It’s very strange that the db_name the script needs to access is ‘archivio.archivio’. There’s a duplication of the db name, I have a db named ‘archivio’ not ‘archivio.archivio’.

So, what’s the problem?
I didn’t change mysqlhotcopy during last few months, but I updated my ubuntu just few days ago and the new DBD version is 4.0004 instead of older 2.9xxx.
Newer versions of DBD::mysql seem to prefix the table names with the database name causing mysqlhotcopy to fail. This seems to happen after version 4.0003

Now I have just two solutions: …