Monitor your databases for availability and performance

There are a thousand reasons why your databases may go offline or perform poorly. And when this happens, your customers will get poor service or no service. Your business suffers.

SQLHealth monitors SQL Server, PostgreSQL and MySQL databases and provides alerts and analysis when something isn’t right. It keeps things simple, so you don’t have to spend your time learning and managing a complex toolset.

Who is SQLHealth for?

Developers - who build applications on popular relational databases and want to understand how their code impacts the database before it goes into production.

Support Engineers - who need to be alerted in real-time when something isn’t right, and who need analysis and advice about how to fix problems.

Infrastructure managers - who are responsible for the availability and performance of their databases and want a simple and cost-effective monitor solution.

How do I get SQLHealth?

SQLHealth is still in development, this is a pre-launch site dedicated to sharing information about SQLHealth 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 “Early Access” box above and we will contact you in the near future when it is ready to trial.

What does SQLHealth focus on?

  • Availability

    Knowing that your databases are online and responsive is the first step in be. confident in the service your applications provide customers. SQLHealth tests that your databases are responsive, and how quick they respond. Should there be a problem SQLHealth will contact you and your team by email and sms.

  • 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. SQLHealth 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. SQLHealth baselines query behaviour and alerts you to significant changes.

  • Locking and Blocking

    Understanding what is being locked and blocked in your database is the basis for building in performance and resilient.

  • Deadlocks

    The curse of every database, when they occur you want as much analysis as you can getyin order to locate and redesign the offending behavour.

What databases does SQLHealth 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.

SQLHealth 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. SQLHealth 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 SQLHealth 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 SQLHealth 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. SQLHealth 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.