The MySQL marketplace today is far more complex then simply choosing between a particular version of MySQL that Sun/MySQL produces.
The MySQL server product in general is released under the GNU General Public License (GPL) v2, however you should carefully review the MySQL Legal Policies as a number of exceptions and different license agreements operate for companion tools such as MySQL Cluster, MySQL client libraries and documentation for example.

Looking into the MySQL ecosystem for products, I’ve produced the following categories:

• Sun/MySQL Official Products
  • MySQL Versions
• MySQL Variants
  • Community
  • Enterprise
  …

I’ve just started using the CSV engine for a practical application and I’ve come across a few subtle and unexpected issues/limitations.

First, you can’t create any columns in your CSV table nullable.

mysql> create table t1(i INT) ENGINE=CSV;
ERROR 1178 (42000): The storage engine for the table doesn't support nullable columns

RTFM shows this was introduced in 5.1.23. See CSV Limitations

The second and more annoying was creating a CSV table, inserting a sample row (just to check the syntax), then replacing the file ([datadir]/[schema]/[table].CSV) with the same format, but with additional generated rows. This was to no avail when attempting to SELECT from the table.

The solution was to do a REPAIR TABLE [table] in order to see the newly refreshed data.
Futhermore, some more RTFM shows in …

The March NY MySQL Meetup featured a presentation from Infobright, a data warehousing solution built on the MySQL Product.

With a pitch of “Simplicity, Scalability and low TCO” I became more impressed with the capability to delivery on these as the presentation proceeded. Here are some highlights.

• The company and product has been around for a few years. Infobright started as a compression engine to sit beside Teradata, providing a significant cost saving to clients, and allowing a two way data transfer between Teradata.
• In September 2008, a open source community edition was released, called ICE. (Which I didn’t know)
• The technology is based on a Rough Set theory, a mathematical approach
• Using a …

As I referenced in my prior entry, I'm reviewing Sun's three major strategic imperatives, and our progress going in to next fiscal year. Our strategic imperatives, in order, are:

1. Technology Adoption
2. Commercial Innovation
3. Efficiently Connecting 1. and 2.

This entry focuses on the second, Commercial Innovation, and reviews our core revenue products, services and strategies.

By now, you understand Sun's approach to growing the market - driving adoption of key technologies drives Sun's addressable market. Once you're using one of our fundamental technologies, Sun's innovations focused on those technologies are relevant to you. The beauty of free distribution is you don't have to pick customers, they pick you.

Three very …

Monitoring MySQL Memory is a rather critical task because you can’t limit MySQL’s usage of physical memory resources. Improperly configured servers running MySQL can crash because you don’t understand memory usage.

MySQL uses memory in a number of different ways. Using the Oracle analogy, you can divide the mysqld memory usage into main areas of:

• SGA - System Global Area
• PGA - Process Global Area

The SGA is the footprint that MySQL uses for startup. This is attributed to the base footprint of the mysqld process and a number of buffers including:

• key_buffer_size - For MyISAM Indexes (note you can define multiple key_buffer’s The MyISAM Key Cache) …

Two more adoption stories; they both use GFv2 and MySQL Server, but while one is a traditional Java EE story, the other is a Rails App ported from Mongrel.

The MidwifeMate application spans the web tier (JSF/Facelets), EJBs and JPA. They use Hibernate talking to a MySQL Server and develop on Eclipse using the …

I have raised this specific topic 3 times this week alone, twice in a MySQL setting.

The fundamental philosophy of testing is NOT to verify features of your product that work, it is to BREAK your system.

One such discussion this week was with a service provider that deployed a new system into an existing ecosystem. The release has been delayed due to development issue, and credibility with customers is now being further damaged because the system is reaching physical hardware limitations after just one month.

With this was described to me, my simple response was. You did not test you system to stress the system to breaking point. To know the limit of your capacity ahead of time is a proactive analysis, not a reactive one.

It’s not that complicated to do, easier in early stage before you have a 50-100-1000 server total environment, but it’s a best practice not see often enough.

As I referenced in my prior entry, I'm reviewing Sun's three major strategic imperatives, and our progress going in to next fiscal year. Our strategic imperatives, in order, are:

1. Technology Adoption
2. Commercial Innovation
3. Efficiently Connecting 1. and 2.

This entry focuses on the first, Technology Adoption. Adoption is a non-economic phenomena, no money is spent, only time - yet it has extreme financial consequences. Let me give you an example.

I was with a big customer of ours last year, and reading through my account briefing before the meeting, I knew we were doing well. An analysis of their download activity showed they were heavy users of Solaris and OpenSolaris, and they had a large internal community of MySQL users, as well. In the meeting, their CIO said "we love where Solaris is headed." I …

Correctly managing your MySQL database objects such as schemas, tables, indexes, base data etc, is critical to the success of a 24×7 online website. I rarely encounter a robust working solution as part of my consulting so I would like to share my experience in identifying the best practices you should be adopting whether your an existing organization or just an individual with a simple website.

Much of the following concept actually pre dates my involvement in MySQL (since 1999), so this is not just applicable for a MySQL RDBMS. For the purposes of this discussion I’d like to focus on the theory successfully used with clients.

Under version control I have the following directory structure:

NOTE If your first observation was “Arrh, Version Control?”, you are in more trouble then you want to be right from day one. You need Version Control such as svn, cvs, bzr, git etc for any website no matter how small.

We've been making a fair number of announcements recently - on both the product and the partnering front. That's generated a lot of interest, and a fair number of questions. So I thought I'd take the opportunity to deliver this overview and the upcoming focused discussions on what makes Sun tick in a video format. Let me know if this is useful, or what else we can do to keep you informed via the comment field at the bottom.

We're approaching the end of our fiscal year, and given all the swirl in the economy, I thought it worthwhile to restate where Sun's headed as a company, to let customers, partners, employees and investors see and understand where we're headed. Clarity's always useful, doubly so in times of uncertainty.

Let me start by joining the chorus of those worried about the global economy. I am routinely talking to customers now partially owned by governments, whose share prices have declined 95% or more, whose balance …