Database Connections
A connected database turns an engagement's numbers into live, verifiable facts. It powers the Database KPIs in Plan and the database path of Ask the Data — and crucially, every result carries the query that produced it.
Who can access
Members of the engagement team.
How it works
Once a database is connected to the engagement:
- Database KPIs are computed live and shown in Plan, each backed by a verifiable query.
- Ask the Data can answer natural-language questions by translating them into a query against the database, returning the result alongside the generated query.
Because every number comes with its query, you (and the client) can see exactly how it was computed — the gold standard for defensibility.
Step by step
- Connect the database via Connected sources (or firm-level Integrations).
- Open Plan → Database KPIs to see computed KPIs with their queries.
- Use Ask the Data to ask ad-hoc questions of the database.
- Verify the query behind any number before it goes to a client.
Best practices
- Inspect the query for client-facing numbers. It's right there — confirm the logic.
- Keep credentials current. A lapsed connection means stale or empty KPIs.
- Distinguish from spreadsheet KPIs. Database KPIs are live; financial KPIs from uploaded spreadsheets are a separate path — see Ask the Data.
Common errors
| Symptom | Likely cause | What to do |
|---|---|---|
| KPIs empty | No database connected, or connection lapsed | (Re)connect in Connected sources |
| A question returns nothing | The question doesn't map to the data, or no DB connected | Rephrase; confirm the database is connected |