Changes (as compared to 2.83) includes:

Features:

* This release adds a ‘base time’ setting in MONyog. This setting (if defined by user) will be used for calculation of uptime-based counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, specific server status variables will be reset to the same value as would be after a server restart. However the ‘uptime’ status variable itself is not affected by FLUSH STATUS. And as uptime-based counters will relate the value of cumultive status variables with some intial time, using the ‘uptime’ variable as the initial time will result in calculation of misleading values if FLUSH STATUS was executed. So to get true uptime-based counters in MONyog with servers that do not support the ‘uptime_since_flush_status’ variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do - not ENTERPRISE servers …

It sounds like a strong argument when a developer states that his company is using its own products, like "MySQL Workbench is using MySQL Connector/C++" or "Connector/OpenOffice.org is based on Connector/C++". But at the end of the day you will need to try out the product yourself. You need to evaluate if its any good for you. Here you go with in-depth build, configure and debug instructions for the MySQL driver for C++ including an example of writing programs that use the driver.

Contents

• Build requirements
• …

It sounds like a strong argument when a developer states that his company is using its own products, like "MySQL Workbench is using MySQL Connector/C++" or "Connector/OpenOffice.org is based on Connector/C++". But at the end of the day you will need to try out the product yourself. You need to evaluate if its any good for you. Here you go with in-depth build, configure and debug instructions for the MySQL driver for C++ including an example of writing programs that use the driver.

Contents

• Build requirements
• …

Update:

This post hit Reddit and now has 10k views. This post was written for the MySQL community who pretty much already read my blog and know that I support MySQL (we use it in production, document bugs, contribute patches, etc).

While Postgres is a great database, MySQL still has a number of features that Postgres doesn’t have. One good example is the use of multiple storage engines (PBXT, InnoDB, MyISAM, etc).

The entire point of this post was to encourage Sun/MySQL to focus on the quality and stability of their releases.

Everyone I talk to who works for LARGE MySQL installations is complaining about the lack of quality and scalability. These problems need to be fixed not routinely swept under the rug.

Original post:

Let’s say we wanted to destroy MySQL. Basically, …

A nice blog from the AWS team describing what's new with SimpleDB now that it's going into public beta. SimpleDB makes it easy to scale. You don't have to worry about creating a complex master-slave setup to support a high level of concurrent access. In fact, concurrent access is where the SimpleDB model really shines. Fire up a bunch of threads and start sending requests our way. SimpleDB can handle the load. In fact, during the private beta the developers at Pluribo scaled their application up until it was making 5600 requests per second Some things to note:

• 60 day free trial for up to 1GB of data
• 30 day free trial of the Simple DB Explorer, including upload of MySQL data into SimpleDB
• Tools for various languages, including Java, Python, Ruby, and ActiveRecord
• Queries can include sorting on any attribute
• Coming soon: a SELECT-like API and batch loading

Looking …

Recently, MySQL introduced the MySQL Query Analyzer tool, which can help DBAs resolve performance problems in their SQL code.  The tool monitors query performance and shows SQL code that is causing a slow down without relying on the slow query log.  DBAs can take this information and use it to further tune their environment to achieve better performance.  You can watch a small demo here to see the product.  Note that the Query Analyzer tool is available with MySQL Enterprise.  A trial version of MySQL Enterprise can be downloaded for 30 days at http://www.mysql.com/trials/.

Tokuview (http://blogs.tokutek.com/tokuview/iibench/) is building a test scripts/program for 1B record insert performance.  This is fine, but ultimately the logistics of the DB environment will dictate what ‘tricks’ can be pulled to insert records the fastest.  Can you access raw MyISAM files or not?  Are you running concurrent inserts?  Do you require ACID compliance? There are 3 basic [...]

Startups are increasing their use of open source products in some shape or fashion. Can we correlate these actions with the demise of the traditional software business model? READ MORE

Certification Magazine has published their 2008 salary survey. But it is more than just a salary survey. Responses from more than 150 countries revealed some very interesting information.

Who has the certifications: 60% percent of those surveyed were in their current job for less than four years. The majority were in IT for less than a decade. But the majority had at least three certifications:

Who paid: 48.3% have their employers pay for their certifications.

How did they study for their exams: Over 48% used self-study books. Practice exams and on-the-job training were used by over 66%. About 75% viewed their prep materials as good or better.

What are they being paid: Figure 7 …

In the next upload of MySQL 5.1.30 to the experimental branch of Debian we are going to drop MySQL Cluster support from the standard MySQL packages. I already wrote something about the future of MySQL Cluster in Debian a while ago, this is just the first step towards a separate mysql-cluster package in Debian.

This change does not (and will never) affect the MySQL packages in etch and lenny, and unstable not until we decide to move MySQL 5.1 from experimental to unstable.