I’ve made slight changes to the site should it interest anyone. The link to mysqlsniffer has been removed (though the page is still there). The links to Optimize and Intricacies have been consolidated into Documents. And the Feedback link is now Contact. Tragically exciting.

Dan Farber reports on IBM's $1.5 billion security push, dubbed "an enterprise free of fear." (Note to IBM: "Free from fear" would be the more direct way of saying it.) But IBM, like others, is approaching security as code an enterprise would layer on other code, and processes on top of that code, rather than something inherent in the code itself, as Stuart McIrvine, director of IBM?s Corporate Security Strategy, relates:

"Our approach is that security is kind of broken. Companies are leaving security in the hands of IT and operations people, looking at servers, databases and putting up firewalls and updating antivirus signatures. But they have no real view of what they are protecting from a business strategy viewpoint, understanding the core objectives and risks to meeting those objectives."

...

On GTAC 2006 (which was called LTAC in those days), I met Adam Porter, professor at UMD and heard his talk about his project Skoll. Skoll is a system for continuously assuring the quality of software under different configurations while intelligently choosing which to run and thus basically saving time. Amazing stuff!

During that time, MySQL was looking for an easy way to integrate more people from their community into their QA process and started the …

On GTAC 2006 (which was called LTAC in those days), I met Adam Porter, professor at UMD and heard his talk about his project Skoll. Skoll is a system for continuously assuring the quality of software under different configurations while intelligently choosing which to run and thus basically saving time. Amazing stuff!

During that time, MySQL was looking for an easy way to integrate more people from their community into their QA process and started the …

Dear LazyWeb,

Please provide insight :)

I am wondering what the common beliefs are regarding C++ file extensions. To come up with an answer I have decided to take a poll (which will not only be unscientific, but probably biased to those who care enough to hit a submit button).

View Poll: #1080838

If you can not see the poll then you are not viewing this post on Livejournal (so go see the original post).

This has nothing to do with MySQL... though I am sure more then a few of our developers have an opinion on this :)

Having a strategy for failover has become almost standard in the business world. Whether it is a total site failover from a NOC in one city to another, or just a simple redundant server. Over the years many technology solutions have been created for or adopted to MySQL to provide this type of strategy.

MySQL AB today announced that the new Sage 50 HR 2007 software suite is now shipping to small businesses in the UK with embedded MySQL database technology. The announcement was made this morning at the Sage Visions 2007 conference in Telford, UK, and follows a global agreement between the Sage Group plc and MySQL AB signed last year. Sage also plans to embed MySQL into two other products, Sage 50 Accounts and Sage 50 Payroll, which plan to ship this time next year.

In the spirit (pun intended) of Halloween, Hyperic sponsored a Nightmare on Web Street contest, where folks were encouraged to tell their grim tales of IT woe for a chance at trick-or-treating for a Wii! The day has come, and the contest winner has been selected. Without further ado, I would like to congratulate “Mr Anderson” for his nightmarish tale of servers and HTML. Here’s the winning entry folks:

Oh by the way, your websites will no longer be hosted in 4 days

In spring of 2002 I was called in by a Company to help them with their websites (I wasn’t an employee at that time, I had a small shop of about 10 guys doing web development/business systems).

The issue? Their Host went bankrupt and they had 4 days to move 100+ sites with 50+ pages each off their servers before the plug was pulled.

If this didn’t go …

Microslow patch is used by many DBAs and developers to accurately time their queries and to catch those which run less than a second as they can also be a performance killer for a busy application.

Recently I have started the development of an updated version of the patch. The basic idea is the same as for its predecessor - to get more information about query execution logged into slow log, however the new version is loaded with a set of cool new features.

CONNECTION IDENTIFIER

Each slow log entry now contains a connection identifier, so you can trace all the queries coming from a single connection.

PLAIN TEXT CODE:

1. # Thread_id: 4

MICROTIME RESOLUTION QUERY TIMING

This is the original functionality offered by Microslow patch. The new edition is free of a tiny bug which was to treat long_query_time value as seconds. In effect …

We were using replication to deal with certain queries that were producing table scans. I realize this is not a great long term solution but we were migrating a web site that was set up this way, so it wasn’t really a choice.

We had a database that was a mix of InnoDB and a few MyISAM tables. The MyISAM tables were used for fulltext searches.

To get a database dump, we were using the command
mysqldump --all-databases --single-transaction --master-data=1 > dumpfile.sql

We’d then import the dump into a DB slave. When we’d bring a slave up and reply the log, we’d get a duplicate key error. After a few times, we noticed it was always on the MyISAM table. This is because MyISAM does not use transactions, and –single-transaction does not place a read lock on tables. Data can be inserted into the table during the backup but before that table is dumped.

In conclusion, if you’re using …