I am happy to see that SkySQL, a new home for MySQL talents, is being
formed.
SkySQL is being
lead by Ulf Sandberg, who was fundamental in building up the
MySQL support, training and consulting organization at MySQL AB
and will employ many of the original and best MySQL
talents!
During the last 2 years, I have seen a lot of the people that
originally worked at MySQL AB and who joined Sun together with
me, go away in different directions.More than 50 % of them have already left
Sun/Oracle. Even if many of them are still working with something
that is related to MySQL, others have started new careers doing
something completely different.
I have done my best to keep the MySQL core development talent …
Configure MySQL Server nodes for MySQL Cluster
The new version of MySQL Workbench (5.2.25) has just gone GA – see the Workbench BLOG for details.
So what’s the relevance to MySQL Cluster? If you have a Cluster that uses MySQL Servers to provide SQL access then you can now use MySQL Workbench to manage those nodes:
- Start & stop the mysqld processes
- Configure the per-mysqld configuration data held in my.cnf or my.ini
The reason that I describe the support as ‘partial’ is that these MySQL Servers are treated as independent entities (no concept of them being part of a Cluster) and there is currently no way to use it to configure or manage the other Cluster processes (data and management nodes). Having said that, what is …
[Read more]Dear MySQL Users,
We’re pleased to announce the release of MySQL Workbench 5.2.25 This release is GA (Generally Available). We hope you will make MySQL Workbench your preferred tool for Design, Development, and Administration of your MySQL database applications.
Special thanks go to all the great MySQL Beta Testers that provided valuable ideas, insights, and bug reports to the Workbench Team. Your beta feedback truly helped us improve the product.
MySQL Workbench 5.2 GA provides:
• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)
Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.
To get started quickly, please take a look at …
[Read more]In my last post, I discussed how to troubleshoot InnoDB locks using the new InnoDB Plugin’s new Information Schema tables.
However, that got me to thinking about how many MySQL 5.1 users who have still not switched to use the plugin as opposed to the built-in version of InnoDB.
There are many advantages to using the plugin as opposed to the built-in version (aside from just the new I_S tables, and more importantly, numerous performance enhancements), and it’s breeze to set up, so I wanted to provide a quick start guide to using the new InnoDB plugin.
Note that the …
[Read more]- Conflict Minerals and Blood Tech (Joey Devilla) -- electronic components have a human and environmental cost. I remember Saul Griffith asking me, "do you want to kill gorillas or dolphins?" for one component. Now we can add child militias and horrific rape to the list. (via Simon Willison)
- Meteor -- an open source HTTP server that serves streaming data feeds (for apps that need Comet-style persistent connections). (via gianouts on Delicious)
- …
A bit less than a year ago I last did a presentation about a telephone book application where we used SQL to do some fairly advanced filtering over about 30 tables of data. The app generated SQL statements that filled pages, the more terms the more pages, but on a 10k dataset it still came back within a few milliseconds, thanks to a ton of indexing and denormalization tricks (SQL Server is a lot more powerful here than MySQL) I had applied. Now in a more recent project I am dealing with 10M+ dataset running on MySQL and so decided to learn about Solr. Wow, that thing is amazing and way more flexible in terms of query language than I expected. As a result I do not see it any more for just projects that are too big for an RDBMS, but more as the way to do search …
[Read more]
One extremely useful feature in MySQL is the "slow query log". In
the stock distribution, it records every query that takes more
than 1 second to execute, and every query that requires a full
table scan. A useful part of the Percona patches extend this
feature to measure sub-second slow queries, which became
important as machines got faster.
When someone asks "Why is the database slow?", the first counter
question to ask is "What's in the slow query log?"
One of the confusing parts of administering MySQL is that the
"query log" and the "slow query log" are different things. They
have different controlling options, and different log
formats.
When I ripped out and replaced the logging system during the
Drizzle fork, I took these two logging systems, which were
implemented as completely separate code, and merged them
together. There is now only the "query log", but it can be
filtered in-process to only …
Answering questions asked on the site.
Frode Underhill asks:
I have some applications that are logging to a MySQL database table.
The table is pretty standard on the form:
timeBIGINT(20)
|
sourceTINYINT(4)
|
severityENUM
|
textVARCHAR(255)
|
---|
, where source
identifies the system that generated
the log entry.
There are very many entries in the table (>100 million), of which 99.9999% are debug or info messages.
I'm making an interface for browsing this log, which means I'll be doing queries like
SELECT * FROM log WHERE source = 2 AND severity IN (1,2) AND time > 12345 ORDER BY …[Read more]
There are few things one is supposed to know about MySQL replication in production, as manual doesn’t always discuss things openly.
This is small set of rules and advices I compiled (some apply to statement based replication only, but row based replication may benefit from one or two too):
-
Don’t use MyISAM. Or in fact, don’t use any
non-transactional engine, if you care about your data. On
either side, master or slave, or both – using non-transactional
engines will cause data drift, as partially executed statements
on master would be fully executed on slave, or simply stop
replication. Of course, every crash has the capacity of getting
your tables desynced from each other and there are absolutely
no guarantees.
This “don’t” can be easily transformed into “do” – just use InnoDB. Bonus point – one doesn’t need to take down the server, to clone a slave from …
I was spending my Midsummer holiday again in the nice Finnish
archipelago of Biskopsö, Nagu together with 30+ friends. As
always there was a lot of good food (Fish first, meat later) and
lot of drinking (Snaps (in various forms, including Salmiakki),
beer, wine and Cognac).
What was new was that we had Felix Schupp, from blackray as a guest
with us.
As a proof that we also know some other drinking song than the
(in)famous "Helan går", we did sing for Felix a drinking song
targeting database users:
To be sung to the music of 'Yesterday':
Yesterday,
All those backups seemed a waste of pay.
Now my database has gone away.
Oh I believe in yesterday.
…