Collaborate 2011 is a database operational conference to be held in Orlando, Florida April 10th - 14th 2011. Unfortunately, the O'Reilly MySQL Conference has been scheduled for the same week; however, I am working with the conference committee to make sure that speakers that want to attend both are scheduled appropriately (I intend on going to both!). The call for presentations is now open through the end of September, so you have just over a month to submit your proposals. Experience has shown that the best presentations are submitted well in advance of the deadline -- I guess when folks are time-crunched by the deadline they do not make such great abstracts....Speakers whose presentations are accepted receive free admission to the conference and a speaker thank-you gift.
When running query against a database the following error can be generated:
ERROR 2006 (HY000) at line NNN: MySQL server has gone away
Where "NNN" is the line number of the script currently being run where the error occurred.
Possible Causes and Resolution
This is a general error which can have a number of possible causes. The one certainty is that the MySQL database is no longer listening on
ODTUG invited me to give a webinar and I said yes, so this Thursday you’re invited to join me as I talk about MySQL performance. We’ve come a very long way towards a MySQL that can perform well on modern hardware, and there really isn’t broad recognition of this. A lot of the best work has gone into the InnoDB “plugin” storage engine, which was announced after my co-authors and I sent High Performance MySQL to the press.
Bug reports can be fun. They can also be terrible. Either way they can be entertaining. On the Drizzle IRC channel today I saw a couple references to MySQL bug reports: it is stop working and Does not make toast (which reminds me of the Mozilla bug report about the kitchen sink). Got any other favourites?
A new version of Kontrollbase – the enterprise monitoring, analytics, reporting, and historical analysis webapp for MySQL database administrators and advanced users of MySQL databases – is available for download. There are several upgrades to the reporting code with improved alert algorithms as well as a new script for auto-archiving of the statistics table based […]
Slowly the power of mysqlnd plugins becomes visible. Mysqlnd plugins challenge MySQL Proxy and are often a noteworthy, if not superior, alternative alternative to MySQL Proxy for PHP users. Plugins can do almost anything MySQL Proxy can do - but on the client. Please find details in the slides. The presentation has been given today at the PHP track at FrOSCon.
View more presentations on mysqlnd.
The biggest news is …
[Read more]Slowly the power of mysqlnd plugins becomes visible. Mysqlnd plugins challenge MySQL Proxy and are often a noteworthy, if not superior, alternative alternative to MySQL Proxy for PHP users. Plugins can do almost anything MySQL Proxy can do - but on the client. Please find details in the slides. The presentation has been given today at the PHP track at FrOSCon.
View more presentations on mysqlnd.
The biggest news is …
[Read more]This week will be my final week at Oracle. I am very much going to miss the great team I work with but due to many other reasons I have decided to move on.
Where am I going?
I'm sure several people already know, if you don't, this will be revealed soon. It will still be related to MySQL, but not so much MySQL Cluster. I do fully intend to still write patches for MySQL and MySQL Cluster in my spare time and I'll still probably be lurking in the MySQL Cluster mailing list and forums.
What does this mean for this blog?
In all likelihood it will become stale very quickly (worst case it will be removed). I will no longer be able to edit it.
Will there be a new blog?
Yes, at some point soon. Watch out on Planet MySQL.
I have recently moved on from my roll as a Senior MySQL Support Engineer at Oracle to a Drizzle Developer at Rackspace. As such my previous blog is now sitting idle so this is the replacement.
This new blog may have much less MySQL Cluster content, but I do hope to continue the same quality (I shall leave you to judge on how high that is!) of blog posts.
It's frustrating seeing examples of MySQL being slow as an example of why you should use NoSQL. If you have an invested interest[1] in comparing two technologies that are already apples to oranges, the least you can do is optimize both. If you can't do it, don't share it.
This came out of a talk on Cassandra. "MySQL" is not on the slide, but it was mentioned in reference to MySQL:
SELECT * FROM tweets WHERE user_id IN (SELECT follower FROM followers WHERE user_id = ?) order by time_tweeted DESC LIMIT 40;
Let me simulate that for you:
CREATE TABLE `tweets` ( `id` int(11) NOT NULL AUTO_INCREMENT, `user_id` int(11) NOT NULL, `info` text, `time_tweeted` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`), INDEX (time_tweeted), INDEX (user_id) ) …[Read more]