AccelerUpDocs
Data warehouse/Overview

Data warehouse

Query the warehouse from AccelerUp — and alert on what the query returns.

The Data Warehouse section connects AccelerUp to your analytical databases so business data sits next to operational data — and, more importantly, so you can alert on it.

Connections
ClickHouse, Postgres, MySQL — read-only, per organisation.
Explorer and SQL Lab
Browse the schema; write and run queries.
SQL alerts
The most capable alerting in the product.
Dashboards
Charts from saved queries.
Scheduled queries
Run on a schedule, export or notify.
KPI reports
A daily digest to Slack, with an AI summary.
Data quality
Freshness, nulls, uniqueness, row-count drift.
Lineage
What feeds what.
Cost monitor
What the queries cost.
Query audit
Who ran what.
Superset
Embedded dashboards.

Why a monitoring product has this

Because the most important alerts are usually about business data, not infrastructure.

"Payments reconciliation is off by more than 0.1%" matters more than CPU on any box, and the only place that question can be asked is the warehouse. A monitoring product that cannot ask it leaves the most consequential checks to a cron job nobody maintains.

Start here

  1. Connect a read-only user.
  2. Explore the schema and write a query.
  3. Turn it into a SQL alert.

The recipes page has working queries for the checks most teams want first — freshness, reconciliation, drift and error rate.

Safety

Every query is validated before it runs: read-only statements only, a two-minute timeout, and a row cap. Connections use credentials you control — give them a read-only user and the point is moot.

Part of Data warehouse — Querying the warehouse, and alerting on what the query returns.