A new MySQL Virtual Appliance is now available for download.

This new virtual appliance runs MySQL Version 5.0.1 which provides some great new features, including new datatypes, support for schemas, increased performance and triggers.

As well, this is the first virtual appliance featuring fully automated use of extra Virtual Hard Disks, which opens the door to practically unlimited storage potential using a small appliance, in spite of a small disk image size.

Any VMware or Virtual PC VHDs working, including physical volumes and VI3’s ESX hosted
iSCSI or Fiber Channel SAN volumes.

We will post a pictorial on how to use VHDs shortly.

As usual, our download images are nice and tiny.  Just 27MB for all this MySQL goodness.

Driver Manager 

The ODBC Driver Manager (DM) provides some very important features to the application. Here are some highlights;

• dynamic binding to driver
• ODBC version mapping (data and calls)
• UNICODE/ASCII translation
• cursor emulation
• ODBC rule enforcement (state transition violations etc)

The vast majority of applications will use the DM. A C/C++ application uses the DM by linking to it (the DM is a library) at build time.

No Driver Manager

In some cases the DM is not important - or is even ‘in the way’. This may be the case when;

• an application wishs to take advanatge of the code portability ODBC offers but wishs to build the code to work with just one database product
• there is a need to reduce the dependencies/complexities of the application - perhaps for performance …

MySQL AB today announced that Toto-Lotto Niedersachsen GmbH has standardized on MySQL® for all its appropriate future IT needs. The German lottery company based its selection on the success it has had using MySQL Cluster to run its online business applications.

Some people who know I’ve used Gentoo asked me my thoughts on using it for MySQL servers. Here are my opinions and experiences while using Gentoo, both for desktop systems and for servers. This is long, but hopefully the brain dump is useful to you. I have so many thoughts on this subject that I’m having a hard time really organizing them well, and I’m censoring myself too because I know I represent only a very small, focused viewpoint on Gentoo.

I posted this over the weekend:
http://download.tangent.org/memcache_engine-0.3.tar.gz

Table spaces are now supported and it works with multiple servers out of the box. This is still very experimental.

Project URL:
http://tangent.org/index.pl?node_id=506

Few days ago I’ve started new site which name is BestTechVideos.com. I’ve created this site because there are lots really interesting videos on the Net, but if you’d like to fine some good tech video, it is not so simple to find them because of tons of crappy “funny videos” like “funny cats” and so on.

So, If you like to attend technical conferences and watch conference sessions on video, if you like idea of screencasts, etc, then this site is for you! Welcome to Best Tech Videos you’ll be impressed by amount of hi-quality and useful videos on the Net.

P.S. If you like this site idea, support it on Digg.com, please. Great thanks in advance.

MySQL offers one of the most complete selection of application programmer interface support. Some of these are in the form of a library (such as the MySQL C API library) while others are in the form of a driver (such as the ODBC driver). For most people/situations - the choice of which interface to use is obvious as it is often dictated by the programming language in use (JDBC for Java for example).

Here are some reasons for considering the ODBC interface. Note; some of these reasons can apply to more than one interface.

• Cross-database
• Cross-platform
• SQL Standard
• C/C++ Programming Language

Cross-database

The ODBC standard was created primarly to provide an application developer with a database vendor neutral way to work with a database. In other words the source code does not have to change just because one decides to switch from (for …

So I am currently working on a MySQL server that is showing behavior as depicted in the following graph.


There can be several possible reasons for these sudden drops. I am working on the issue and will be posting the results. Have you experienced something similar?

A quick refresher on the locations MySQL uses to load up configuration options on Unix:

1. /etc/my.cnf
2. $MYSQL_HOME/my.cnf (sometimes this is your datadir, other times it's basedir)
3. command line arg (defaults-extra-file)
4. user's home directory (~/user/.my.cnf)

It's available in the MySQL docs, and there's a section on it in Pro MySQL, but it seems a need to remember the exact order only comes often enough to confirm that I haven't committed it to long-term memory.