MySQL

The world's most popular open source database

Contact a MySQL Representative


  • MySQL.com
  • Developer Zone
  • Partners & Solutions
  • Customer Login
  • DevZone
  • Downloads
  • Documentation
  • Articles
  • Forums
  • Bugs
  • Forge
  • Blogs
 
  • Pages

    • About me
    • Bio
    • Press Release: “Kaj Arnö Appointed MySQL VP of Community Relations”
  • Blogroll

    • Ein Finnlandschwede in Bayern
    • En finlandssvensk i Bayern
    • It’s some interesting topic
    • Kaj Arnö blog aggregation
    • No Software Patents!
    • Planet MySQL
  • Recent Posts

    • How we fixed the MySQL.com Power Outage
    • A Remote-Attendee’s Look at OSCON
    • MySQL Librarian: Capturing Community Insights
    • MySQL: Powering a New World Religion
    • The Embedded Reporter in the Half-Marathon
    • Berlin Open 09: Social Networking
    • Search the planetary archives, and tag your blog entries
    • SELECTing SELECT statements for Wordpress MU blogging statistics
    • How do MySQL users keep track of digital pictures?
    • Presenting and blogging in Chinese
    • On the Merits of Voting
    • The Future of MySQL
    • The Great Open Cloud Shootout: Videos and other links
    • Karen’s Commitments to the MySQL Community
    • What hasn’t changed with MySQL
  • Tags

    Alexander Arnö Black Swan Blogging Blogs Brazil Call for Papers Call for Participation CfP Community Contributions David Axmark Event scheduler Football FOSDEM Growth Innovation Ivan Nikitin Language Launch Mårten Mickos Michael "Monty" Widenius Mountains MySQL MySQL 5.1 MySQL AB MySQL Forge MySQL User Conference MySQL Users Conference Nassim Nicholas Taleb Open Source Oracle Paris Partitioning Photography Running Runnism Runnismus Social Networking South Africa Sun Microsystems Sun Tech Days Thank you Travel Twitter Use case
  • Archives



  • Categories

    • Architecture of Participation
    • Connectors
    • Documentation
    • Events
    • Falcon
    • GPL
    • GUI
    • Licensing
    • MySQL
    • MySQL Cluster
    • MySQL Proxy
    • MySQL Server
    • MySQL Users Conferences
    • MySQL Workbench
    • Photography
    • PHP
    • Release Policy
    • Ruby on Rails
    • Running
    • Summer of Code
    • Sun
    • Sun visits
    • Travel
    • Use cases
    • Virtual company
  • Calendar

    November 2008
    M T W T F S S
    « Oct   Dec »
     12
    3456789
    10111213141516
    17181920212223
    24252627282930
Observations by Kaj Arnö @Sun
« Attending MySQL Events in Kiev 26.11.2008 and Moscow 1.12.2008
The Death of the Standalone Document »

The Query Analyzer — a potential Killer App?

There have been plenty of blog entries and writings about the MySQL Query Analyzer, for what I think are good reasons. Labeling it a potential Killer App, causing many MySQL users to become paying Sun customers, may be a daring thing. However, the Query Analyzer might very well have what it takes. The key benefit of it is that it identifies the source of performance bottlenecks. In that sense, one could perhaps instead call it a profiler, as it analyses the set of all queries going on, as opposed to an individual one. One person to whom I described it said “ah, so it’s sort of a DTrace for MySQL queries?” — and for those who know what DTrace is, it’s not a bad analogy.

Some of the key documents and blogs to read includes the overall product description, the Sun PR text, and the interview with Mark Matthews. Do read Mark Callaghan’s review “Query Analyzer Rocks“. Do read Zack Urlocker’s Query Analyzer related business model discussion, where he asks “Can you develop a business model that works for the community and for paying customers?“.

Given the non-FOSS nature of the Query Analyzer, there has also been some community discussion on this, such as Baron Schwartz mentioning an alternative to the MySQL Query Analyzer, followed by Mark Leith’s response to it.

And the non-FOSS nature of the Query Analyzer is something I need to underline, in order not to set false expectations. It is part of the MySQL Enterprise subscription offering. It is not GPL software. So what this means is that you will be confronted with registrations, with trial periods and similar things familiar from other non-FOSS software, should you decide to try it out. You may agree or disagree as to whether that is right or wrong, but that is the business model we’ve chosen at Sun Microsystems (and read Zack’s blog post for some of the underlying reasoning). And while my role as VP MySQL Community is primarily focused at growing and serving the MySQL user base, I am of course also interested in Sun having a business model for MySQL that enables growth in economic terms. I’m excited to see where the Query Analyzer will take us!

So, to sum it up: You may recall various discussions on Sun wanting to serve both the group of people who “have more time than money” and those who “have more money than time“. The value of MySQL Query Analyzer just might be compelling enough for many to count themselves into the latter group.

Links:

  • http://www.mysql.com/products/enterprise/query.html
  • http://www.sun.com/aboutsun/pr/2008-11/sunflash.20081119.1.xml
  • http://dev.mysql.com/tech-resources/interviews/interview_mark_matthews.htm
  • http://mysqlha.blogspot.com/2008/11/query-analyzer-rocks.html
  • http://weblog.infoworld.com/openresource/archives/2008/11/mysql_query_ana.html
  • http://www.xaprb.com/blog/2008/11/20/an-alternative-to-the-mysql-query-analyzer/
  • http://www.markleith.co.uk/?p=22
  • http://www.mysql.com/why-mysql/white-papers/mysql_wp_queryanalyzer.php

This entry was posted on Friday, November 21st, 2008 at 18:27 and is filed under MySQL. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “The Query Analyzer — a potential Killer App?”

  1. Arjen Lentz Says:
    November 22nd, 2008 at 13:48

    I think the query analyser is a good offering. Everybody will have something to like and dislike about it, but I think that both the design and the business decisions around it are within the realm of sane (from my perspective) and thus I applaude it as a good step by Sun/MySQL.

    Question though: what’s going to happen with the “enterprise binaries”? Is that going to continue with 5.1 ?

Leave a Reply

Observations by Kaj Arnö @Sun is proudly powered by WordPress MU running on Blogs.mysql.com.
Entries (RSS) and Comments (RSS).