I've been dealing with a security product from a security company in recent days that breaks best practices with respect to the database configuration. This has reminded me of the list of issues I've seen over the past six months that have raised my ire. I'll rail mostly at products that use SQL Server as the back-end, but I'll save the last example for one that uses MySQL. It's not the database products that are weak. It's the application implementation on them!

Case #1: Don't EVER use SA and don't enable the network if you don't have to!

This said security product recommends the use of SQL Server if you are using it on over 1,000 users. Okay, no problem. It wants its own instance. Okay... that raises a flag in and of itself. Is performance really that bad? Well, no, not likely. Here's the kicker:

To install the application you must use the sa account. Not a service account with sysadmin rights …

I have seen too many date fields that have been named after reserved key words that I need to make an entry for this... It's like naming your kid "Kid". Wait a sec... that's happened many times before as well.I will make a "Proper Naming Conventions" page for mySQL after checking a few more sources first, but this date naming issue cannot wait another day.Thus..First Rule: Do not use a reserved

For a split second, I thought Jonathan said he thought of Sun’s acquisition of MySQL as “hypocritical”. Of course, what he said was “Hippocratical”, in the sense of the old Greek with the oath for doctors: “Do no harm.”

Jonathan appeared in front of the integration team with MySQL and Sun employees here in Menlo Park. What he said was very comfortable to hear for MySQLers old and new:

• Jonathan sees a great strategic fit between MySQL and Sun, and that’s the prime precondition for any good acquisition.
• The strategic fit thinking is seconded by financial analysts and technical observers alike.
• “Honour the community“: Jonathan sees the community of MySQL users as the starting point for all decisions related to the integration.
• “Honour the employees“: Jonathan respects the group of MySQL …

Pentaho Data Integration (Kettle) never was a real transactional database engine, and never pretended to be that. It was designed to handle large data volumes and slam a commit in between every couple of thousand rows to prevent the databases from chocking on the logging problem.

However, more and more people are using Kettle transformations in a transactional way. They want to have the option to roll back any change that happened to a database during the execution of a transformation in case anything goes wrong.

Well, we have been working on that in the past, but never quite got it right… until today actually. As part of bug report 724 I lifted the decision to commit or roll back all databases to the transformation level.

Take for example a look at this transformation:

What happens is …

We just had an internal discussion about if sticking with PHP limits your career options. And just now (coincidence?) I noticed blog posts in the PHP and MySQL community noting similar concerns. The issue is that there is simply not enough top qualified talent that knows LAMP well enough to hire. Or maybe its just too hard to find them? It seems all the good guys are already hired. As a result companies end up looking for other technology, not because they actually believe that these technologies are any better or worth the license fees that these usually require to be paid up ..

So whats the problem here? Well I think one of the key issues is that LAMP focus on solving issues with a very non academic way. This implies that …

We're looking for an experienced and motivated MySQL DBA to help make things go at Flickr.

We're looking for a DBA with strong LAMP background.

Specific Duties:
? Work with engineers on performance tuning, query optimization, index tuning.
? Monitor databases for problems and to diagnose where those problems are.
? Work with Senior DBA to maintain a scalable, reliable, and robust database environment.
? Build database tools and scripts to automate where possible.
? Support MySQL databases for production and development.
? Provide 24x7 escalated on-call support on a pager rotation.

Requirements & Education:
? 3-4+ years MySQL experience.
? 2+ years of experience as a MySQL DBA in a high traffic, transactional environment.
? 2+ years working in a LAMP environment, particularly PHP/MySQL combination.
? Proficient with database performance …

In case you are visiting the MySQL Users Conference & Expo this year (April 14-17, Santa Clara, California, highly recommended), these are the sessions where you can watch Phil and myself presenting about DRBD:

• All bases covered: A Hands-on Introduction to High-availability MySQL and DRBD (3-hour tutorial)
• Database Integrity Protection with MySQL and DRBD (1-hour presentation)

Monty Taylor is also doing a High Availability talk that will be touching upon DRBD to some extent:

• High Availability Landscape of MySQL …

All things come to an end, and so do old software. By removing the older version of the EOL version 4.0 of MySQL from OpenSolaris, we encourage users to go on to 5.0. From build 79 MySQL 5.0 is now integrated into OpenSolaris. Btw, MySQL 4.0 will not go away unless the ARC case is accepted of course.

All things come to an end, and so do old software. By removing the older version of the EOL version 4.0 of MySQL from OpenSolaris, we encourage users to go on to 5.0. From build 79 MySQL 5.0 is now integrated into OpenSolaris. Btw, MySQL 4.0 will not go away unless the ARC case is accepted of course.

Please read the luculent Safe Harbor Statement at the bottom of this page....

We released our official earnings on Thursday last week, after pre-announcing the news one week prior alongside the announcement of our intent to acquire MySQL.

Our second quarter financial announcement came down to this: we doubled our profitability compared to a year ago, with $260 million in net income on revenues of $3.6 billion, while generating $336 million in cash from operations. We also repurchased $750 million of our own shares within the quarter, and reaffirmed our guidance for the full year of low to mid …