An Oracle DBA needs to learn how to manage a MySQL Instance. The MySQL instance has different memory buffers and caches like any database server. Part of MySQL's uniqueness is that it has memory areas to be configured that are associated with different types of storage engines.

MySQL is an database server and anyone managing the MySQL database server has to learn the architecture, and feature functionality like any other database server. The biggest mistake to make with a new MySQL environment is thinking it is a toy and trivial to work with. A MySQL server needs to be properly configured, tuned and managed like any other database server.The key to learning any database

As MySQL continues to explode in the marketplace, there are more Oracle and SQL Server DBAs learning MySQL. For Oracle DBAs, its important to understand that MySQL is a different type of database server.Oracle is the aircraft carrier of database servers. Oracle has by far more features than any other database server. Oracle supports a number of database server solutions such as Real

We just announced the latest MySQL Workbench 5.1 release, 5.1.16. This release was labeled GA, which means that everybody using WB 5.0 or an earlier version of WB 5.1 is recommended update to WB 5.1.16.

We are now putting our main focus on the WB 5.1 branch and will continue to provide rapid update releases during the next months. Please report any hidden issues you may still find on our bug-tracker bugs.mysql.com so we can take care of those quickly.

After the dust settles we will also continue to work on WB 5.2 in parallel, to give you query & administrative functionality within a single, powerful but easy to use tool.

Happy schema designing with MySQL Workbench 5.1!

A short time ago I posted how I was Using XtraDB Backup to backup InnoDB. Overall, the blog post was positive, but experiences that others have had (and commented to on that blog post) have made me want to put out another short article about using XtraDB backup.

The first few points remain the same — the backup process is stable, we were able to use the binaries without compiling, and using Innobackupex as the wrapper script, analogous to Innobackup.pl.

However, we did figure out why Xtrabackup had to be run as the mysql user:

Xtrabackup writes to the data dictionary file (ibdata1, for example). We have not examined if it also writes to the data and index files (still ibdata1 by default, or the .ibd files when using innodb_file_per_table). [EDIT: The authors of Xtrabackup have commented below as to why the write occurs: …

Governments. Governance. Customers wins. And more.

Follow 451 CAOS Links live @caostheory
“Tracking the open source news wires, so you don’t have to.”

Governments
The Examiner provided a two part interview with Daniel Risascher, Office of the CIO, Department of Defense, on open source at the DoD, while Government Technology Magazine reported on how open source software and cloud computing can save government money. Similarly, The UK Conservative party delivered a paper on the future of open standards, open source, SOA and cloud for UK Government, while it was reported that Vienna to …

We’re proud to announce the first General Availability build of our database development tool MySQL Workbench. Version 5.1.16 is now available on our download-servers. On our final run towards GA release of version 5.1 we managed to close 13 bugs and a couple of small issues still found in our previous release. Details on latest changes can be found on our Releases Page. Starting with this release, we recommend to switch from your Workbench 5.0 installation right to the new release (if you haven’t yet) - 5.1 is now our current stable release.

The files for different platforms have been pushed to our main server and will be globally available on our mirrors during the next hours. Please get your copy form our Download page:

…

MySQL Workbench Version 5.1.16 the General Availability build can be downloaded at http://dev.mysql.com/downloads/workbench/5.1.html.Congratulations to the Workbench team for their great effort in this release.

Earlier I reported about two crashes related to MySQL 5.0.22 on Ubuntu 6.06 LTS.

I think those bugs show a lack of testing on the side of Cannonical/Ubuntu. And for MySQL there is a quite good test suite available, so it's not rocketsience.

There are multiple reasons why you could use the MySQL Test Framework:
1. Test if bug you previously experienced exists in the version you are using or planning to use.
2. Test if configuration changes have a good or bad result on the stability of mysqld.
3. Test if important functions still return the correct results (especially importand for financial systems)

$ echo "SELECT @@version;" > version.test
$ cp version.test version.result
$ mysql < version.test >> version.result
$ mysqltest --result-file=version.result …

I see this benchmark being quoted in multiple places, and there I see stuff like:

When carrying out more database benchmarking, but this time with PostgreSQL, XFS and Btrfs were too slow to even complete this test, even when it had been running for more than an hour for a single run. Between EXT3, EXT4, and NILFS2, the fastest file-system was EXT3 and then its successor, EXT4, was slightly behind that. Far behind the position of EXT4 were NILFS2 and then Btrfs and XFS.

There were few other benchmarks, e.g. SQLite showed ‘bad performance’ on XFS and Btrfs.

*clear throat*

Dear benchmarkers, don’t compare apples and oranges. If you see differences between benchmarks, do some very very tiny research, and use some intellect, that you, as primates, do have. If database tests are slowest on filesystems created …