[...] you can also try an approach mentioned here on this page. So, if you have any questions or suggestions, please drop a comment. I will make sure to get back [...]

Thanks Robert. I saw your blog post as well and enjoyed it. I may be testing Tungsten out in the near future.

I, too noticed the comments on Planet MySQL and I am not sure where they are coming from or who to contact to get the comments feed removed.

Hi Aaron, this is a nice article. I referenced it in my own blog article concerning synchronous replication (http://scale-out-blog.blogspot.com/2012/08/is-synchronous-data-replication-over.html). Thanks for doing the experiment.

Meanwhile, I don’t know if you have gotten email from others, but comments on this blog appear as separate posts on Planet MySQL. There might be a problem with your RSS feed settings.

The MySQL 5.6.6 binaries were released today so I decided to take a look at the changelog. I was looking through some of the interesting-sounding new password and security features when I saw this sentence:

The mysql.user table now has a password_expired column. Its default value is 'N', but can be set to 'Y' with the new ALTER USER statement (which also sets the Password column to the empty string).

read more

I'm proud to announce the release of another open source project from myself and my colleagues at Box -- Rain Gauge.  It's puts a nice interface on pt-stalk, and helps manage running it as a daemon on all your mysql servers, so you don't miss the details when your database starts acting up.

What is Rain Gauge?  You can think of it like a web-based pt-sift.  You run pt-stalk continuously on all your database servers; this will watch your mysql process and when a configurable condition is met, then it triggers a host of collections to record what your disks, processor, and memory were doing at the time, along with mysql internal status, processlist and much much more.  It can even kick off GDB backtrace collections and oprofile gathering if desired.
…

Are you to be aware of the Sales Wolf really? Is this something to be scared of? Sean Hull writes a bit about this in a recent post but I think he got a few things wrong, although I also agree with a lot of stuff in there. Above all, I think Sean oversimplifies what Sales are up to.

Before I go on though, let me tell you that I have worked at Oracle, not only as part of the MySQL -> Sun -> Oracle transition but before that, actually my first job outside Telco and my first job for a US company was …

MySQL Connector/Python v1.0.5 beta is now available for download from the MySQL website. This version is feature complete and we welcome and appreciate feedback and bug reports.

We’re also interested in hearing your feedback for future enhancements. Let us know how you’re using the connector too, especially if you are using it with Django, SQLAlchemy and similar Python technologies.

A few things have changed since the last development releases and we hope the manual shipping with the Connector/Python distribution (and also available online soon) will help you get up to speed.

Here are a few important changes that might be incompatible with current scripts using the now obsolete development releases v0.3.2 and …

Read the original article at Beware the sales wolf in sheep suits

Recently a colleague called me up to get my opinion. Therein lies the eternal drama in organizations, the push & pull between dollars and technology best practices. We had a similar experience with a MySQL deployment, and solution framed by Oracle sales. Battle lines are drawn Clearly the battle lines are drawn now. Between director [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

1. Beware the client
2. Open Insights 22 – Beware of Software …

This is the first follow-up to my post on a simple test of KVS alternatives. To recap, I tested a simple single table schema in MySQL using the NDB and InnoDB storage engines. To have a Key-Value store to compare with, I did the same test in MongoDB. All tests were done of the same system, an 8-core AMD Linux box with 16 Gb RAM. The tests consisted of reading 1.000.000 rows, out of the total 105.000.000 in the table, distributed over 100 threads 10 times, a total of 10.000.000 rows read then. The test program I use makes sure that the same random ID's of the table are reused each time and the same are used for all servers.

Now, firstly, after some checking I realized that I had not fully cached the InnoDB engine, so it was doing a certain, small, amount of disk I/O still. I fixed this and the number now looks like …

I’m hosting MySQL Indexes: Best Practices Webinar next week, Wednesday August 15. In which I will talk about how MySQL indexes are structured and how they can be used, as well as go over the best practices in selecting correct indexes for your database workloads.

Indexing looks like a very basic topic, but it is rather deep one. Most people would think they know how to index their database properly but this just applies to basics, and more often than not a lot of opportunities for optimizations are left on the table. You can often get 3x better performance by having your database well indexed, compared to “basically” indexed.

In addition to talking about indexes themselves I will also talk about some query tricks you can use to get MySQL to use indexes when it could not before. This is another tool every MySQL DBA should …