How do I get QueryChimp?

QueryChimp is still in development, this is a pre-launch site dedicated to sharing information about QueryChimp and collecting email addresses of people who would like to be notified when it is ready for beta testing (free of charge).

If you are interested in being notified when our early access program starts, leave your email address in the “register now” box above and we will contact you in the near future when it is ready to trial.

Query execution speed

Knowing which queries in your databases are performing poorly is a key part of maintaining performance. SQLHealth shows you your query execution times mapped against a warning threshold and a failure threshold. Should any of your queries exceed these thresholds, you will be alerted by SMS, mail or both.

Query execution count analysis

Knowing how often different queries are being executed helps you identify where performance improvements may have the biggest impact. SQLHealth shows you execution frequency for your queries (or stored procedures) allowing you to spend your time tunning the ones that are executed most.

Utilisation analysis

What does it look like ?

As a monitoring tool, it uses graphs and charts to summarize information. SQLHealth simplifies the information it receives from your databases and presents this is an easy to digest format that allows you to make decisions quickly. Other database tools can sometimes present too much information, making it hard separate the signal from the noise. SQLHealth focusses on simplicity.

By setting two threshold values, you can group query execution times into three groups. (1) Fast queries that are below the first threshold (2) Queries to watch - that exceed the first threshold but not the second and (3) Queries to work on - that exceed all thresholds.

High level status of all databases

Initially SQLHealth presents you with a high-level status of the health of each of your databases. This takes the form of tiles arranged in groups, with selected datapoints displayed. Each database can have rules configured that determine when to set the status as green, orange or red. The status is based on (a) availability - is the database responding and (b) are all queries performing within configured time limits. What you need to know in one view.

What does QueryChimp focus on?

  • Query Speed

    Slow queries (select, insert, update or delete) can be the cause of poor site or application performance. For most databases, commercial grade software aims for execution times of less than 100ms. QueryChimp will monitor your query execution times and bring to your attention poorly performing queries.

  • Query Frequency

    Some queries execute more than others. These queries are the ones that are often the most important to optimize as this will have the largest cumulative impact on your database.

  • Changes in query behaviour

    Query behaviour can change when code change, database structure and even data. QueryChimp baselines query behaviour and alerts you to significant changes.

What databases does QueryChimp work with?

While the principles of database performance and optimization are shared between all relational databases, there are specific considerations for each vendor’s implementation.

QueryChimp will initially focus on PostgreSQL databases, particularly those running as RDS images in Amazon Web Services (although this will translate to standalone instances of PostgreSQL anywhere). After this, we will focus on support for Microsoft SQL Server, and then MySQL.

Common Questions

  • Sort of. There is no other tool on the market dedicated to just database query performance. There are many very good tools that provide a large range of features to help manage databases - but none are focused 100% on performance. These other tools are complex and expensive. QueryChimp focuses on doing one thing very well at a low price.

  • It is focused on understanding query performance and being simple to use. It is not trying to provide 101 database related features - it is focused on one thing, to help you identify and resolve slow queries.

  • Yes, in order to extract performance data. It requires read-only access and it can operate in one of two modes.

    The first is QueryChimp calls your database and collects what it needs. The second, an alternative, is you can use the stored procedures we have written for you to add to your database and they will collect the required information and send it.

    The first method is easier and faster, the second method lets you see exactly what QueryChimp is doing.

  • Yes, in fact this is one of it’s main goals - to help developers. It will give developers visibility of how their database is performing as they build out their app or service.

  • Yes, it has been designed for exactly this use. By monitoring query execution speeds in real time, it can then provide real-time alerting when performance thresholds are breached.

  • No. QueryChimp uses data already collected by the database engine and stored into system tables.

    All commercial grade databases have a set of system tables that capture different aspects of the system as it is running. QueryChimp uses these tables.