November 19, 2008
MySQL Query Analyzer
Given how the product’s rollout has been handled, it seems necessary to comment on MySQL’s recently released MySQL Query Analyzer without actually having much information on the subject. Mark Callaghan offers a good take — he’s generally very favorable, but notes that MySQL has some limitations that Query Analyzer has trouble getting around.
Comments
2 Responses to “MySQL Query Analyzer”
Leave a Reply
Search our blogs and white papers
Monash Research blogs
- DBMS 2 covers database management, analytics, and related technologies.
- Text Technologies covers text mining, search, and social software.
- Strategic Messaging analyzes marketing and messaging strategy.
- The Monash Report examines technology and public policy issues.
- Software Memories recounts the history of the software industry.
User consulting
Building a short list? Refining your strategic plan? We can help.
Vendor advisory
We tell vendors what's happening -- and, more important, what they should do about it.
Monash Research highlights
Learn about white papers, webcasts, and blog highlights, by RSS or email. |
-
Recent posts
-
Categories
- About this blog
- Analytic glossary
- Analytic technologies
- Application areas
- Buying processes
- Companies and products
- 1010data
- Ab Initio Software
- Actian and Ingres
- Aerospike
- Akiban
- Aleri and Coral8
- Algebraix
- Alpha Five
- Amazon and its cloud
- ANTs Software
- Aster Data
- Ayasdi
- Basho and Riak
- Business Objects
- Calpont
- Cassandra
- Cast Iron Systems
- Cirro
- Citus Data
- ClearStory Data
- Cloudant
- Cloudera
- Clustrix
- Cogito and 7 Degrees
- Cognos
- Continuent
- Couchbase
- CouchDB
- Databricks, Spark and BDAS
- DATAllegro
- Datameer
- DataStax
- Dataupia
- dbShards and CodeFutures
- Elastra
- EMC
- Endeca
- EnterpriseDB and Postgres Plus
- Exasol
- Expressor
- FileMaker
- GenieDB
- Gooddata
- Greenplum
- Groovy Corporation
- Hadapt
- Hadoop
- HBase
- Hortonworks
- HP and Neoview
- IBM and DB2
- illuminate Solutions
- Infobright
- Informatica
- Information Builders
- Inforsense
- Intel
- Intersystems and Cache'
- Jaspersoft
- Kafka and Confluent
- Kalido
- Kaminario
- Kickfire
- Kognitio
- KXEN
- MapR
- MarkLogic
- McObject
- memcached
- MemSQL
- Metamarkets and Druid
- Microsoft and SQL*Server
- MicroStrategy
- MonetDB
- MongoDB
- MySQL
- Neo Technology and Neo4j
- Netezza
- NuoDB
- Nutonian
- Objectivity and Infinite Graph
- Oracle
- Oracle TimesTen
- ParAccel
- Pentaho
- Pervasive Software
- PivotLink
- Platfora
- PostgreSQL
- Progress, Apama, and DataDirect
- QlikTech and QlikView
- Rainstor
- Revolution Analytics
- Rocana
- salesforce.com
- SAND Technology
- SAP AG
- SAS Institute
- ScaleBase
- ScaleDB
- Schooner Information Technology
- SciDB
- SenSage
- SequoiaDB
- SnapLogic
- Software AG
- solidDB
- Splunk
- Starcounter
- StreamBase
- Sybase
- Syncsort
- Tableau Software
- Talend
- Teradata
- Tokutek and TokuDB
- Truviso
- VectorWise
- Vertica Systems
- VoltDB and H-Store
- WibiData
- Workday
- Xkoto
- XtremeData
- Yarcdata and Cray
- Zettaset
- Zoomdata
- Data integration and middleware
- Data types
- DBMS product categories
- Emulation, transparency, portability
- Fun stuff
- Market share and customer counts
- Memory-centric data management
- Michael Stonebraker
- Parallelization
- Presentations
- Pricing
- Public policy
- Software as a Service (SaaS)
- Specific users
- Storage
- Theory and architecture
- TransRelational
- Uncategorized
-
Date archives
-
Links
-
Admin
It should be noted that MySQL Query Analyzer is part of MySQL Enterprise, which is not open source
There’s unspoken non-news related to the MySQL Enterprise Fall 2008 release at conference: MySQL Enterprise is *still* based on MySQL (open source) 5.0, which came out over three years ago, the same month as Microsoft SQL Server 2005! I’m at a loss to understand Sun’s slowness to bring out 5.1 in a GA release.
(I wrote about this a couple of months ago here: http://www.intelligententerprise.com/blog/archives/2008/09/infobright_kick.html .)
The closed-source aspect should surprise nobody.
But yeah, upgrading a DBMS from “sort of adequate” to “really industrial-strength” is haaaard. And it’s not obvious that many of the MySQL folks had done that before setting out along this path.