Microsoft is now offering support for MySQL, which should give pause to every open-source company that expects to make money through support subscriptions.

I hate it when the changelog of any MySQL release references bugs which when clicked, simply says "You do not have access to bug".

Savio Rodrigues has published a post arguing that cloud platforms such as Amazon Web Services and Microsoft’s Azure pose a threat to the monetization of open source by specialist vendors.

Savio makes a good case based on the recent launch of AWS’s Relational Database Service, based on MySQL, and Microsoft’s support for MySQL and Tomcat on Azure:

“When Amazon decided to offer MySQL via Amazon RDS, they did so without purchasing MySQL support from Sun. I’ve confirmed that Microsoft Azure is supporting MySQL on Azure without paying Sun for a MySQL Enterprise subscription.”

Clearly there is a threat to open source vendors from cloud-based services. Meanwhile I have previous …

This is the 170th edition of Log Buffer, the weekly review of database blogs. Welcome. Let’s kick off this week with a double-helping of . . . 

SQL Server

There are lots of good technical posts this week. The SSIS Junkie has some observations and a straw poll on sort transform arbitration. He writes, “This post was prompted by a thread on the MSDN SSIS forum today where the poster was asking how he could replicate the behaviour of SSIS’s Sort transform using T-SQL, specifically he wanted to know how the Sort transform chooses what data to pass through when the ‘Remove Duplicates’ option is checked.”

Another poll, …

Google launches Chromium project, Terracotta acquires Quartz. And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca
“Tracking the open source news wires, so you don’t have to.”

For the latest on Oracle’s acquisition of MySQL via Sun, see Everything you always wanted to know about MySQL but were afraid to ask

# Google launched the Chromium OS open source project, a prelude to the Chrome OS, while Canonical confirmed that it is contributing to the development of Chrome OS.

# Terracotta …

I'm presenting during MySQL Performance Session in Paris which will take place on 24th November in our office building - Sun Solution Center, 32 rue Monceau, 75008 Paris. I did not blog about to avoid to increase frustration for all people who cannot attend it.. Because even we reserved for this even the biggest conference hall in the building there is still not enough place to accept everybody.. As well we did not expect so high interest - the first invitations were sent in priority to MySQL customers, and in few days there was already no more place..

So, why I'm writing now? ;-) Just because I'm pretty sure there will be a second session! :-) I cannot say you date & place yet because it'll directly depend on the number of persons willing to attend. And if you have a such willing, please, right now express it by email to Olivier.Beutels(at)sun.com !

List of topics covered during Performance Session:

…

Hello again.

After I left Pythian I was looking at a couple of other places to begin working with, but finally settled on staying in the mediterranean region, however with a small relocation.

Thus, this post is now long overdue, but I am working for a spanish company called Tuenti, which is the largest social network in spain. I am quite excited and have now settled down in Madrid, so I will be using this website in order to blog about challenges, problems, solutions and everything that comes with running a large scale deployment of MySQL.

Stay tuned for the first technical post, it’s on its way already!

When I developed partitioning for MySQL the main goal was
to make it easier for MySQL users to manage large tables
by enabling them to easily add and drop partitions.

It turns out that partitioning can also be used as a manner
to make MySQL more scalable. The reason is that in some
cases the storage engine have internal locks per table or
per index (one such example is the btr_search_latch in InnoDB).

So in this case adding a
PARTITION BY KEY (key_part)
PARTITIONS 4
to the table definition makes a very hot table into 4 tables
from the storage engine point of view.

This would mostly be beneficial in cases where the main
operation is primary key lookups on the table. Dividing the
indexes in cases of scans can be both positive and negative.
So this solution is definitely not a winner for all situations.

I haven't …

There is the rare bug which I ran into every so often. Last time I've seen it about 3 years ago on MySQL 4.1 and I hoped it is long fixed since... but it looks like it is not. I now get to see MySQL 5.4.2 in the funny state.

When you see bug happening you would see MySQL log flooded with error messages like this:

091119 23:03:34 [ERROR] Error in accept: Resource temporarily unavailable
091119 23:03:34 [ERROR] Error in accept: Resource temporarily unavailable
091119 23:03:34 [ERROR] Error in accept: Resource temporarily unavailable
091119 23:03:34 [ERROR] Error in accept: Resource temporarily unavailable

filling out disk space

Depending on the case you may be able to connect to MySQL through Unix Socket or TCP/IP or neither.
It also looks like there is a correlation between having a lot of tables and such condition.

Previously I was unlucky with seeing this issue in …

My benchmark scripts was upgraded once more today.
I fixed all issues pertaining to full automation
of DBT2 runs. So now it is as easy to start a
DBT2 test run as it previously was to start a
sysbench run. Obviously DBT2 was already earlier
supported in the benchmark scripts, so what I did
now was add the final steps to make it fully
automated. This includes also generating the DBT2
load files needed to load the DBT2 database.

See the download section on www.iclaustron.com
for the tarball including some description of
how to configure sysbench and DBT2 test runs.