SQL Editor gives developers and analysts a direct way to inspect connected data, run SQL, and validate the models used by Analyzer and Dashboard Builder.
- Selecting configured data sources.
- Running read-oriented SQL through the app query layer.
- Inspecting result tables.
- Iterating on SQL models before using them in dashboards or AI workflows.
- Keeping query work close to the same metadata used by Analyzer and Dashboard Builder.
Use SQL Editor against databases you control or are authorized to query. Keep
connection strings and database passwords in .env or deployment secrets, never
in screenshots, examples, issues, or committed files.
SQL Editor keeps interactive query previews bounded so the browser is not asked to render very large result sets.
- Query preview is capped at 1,000 rows.
- CSV export reruns the last successful query and is capped at 100,000 rows.
- If the SQL itself contains a smaller
LIMIT, that query limit still applies. - If the SQL contains a larger
LIMIT, the app caps it to the relevant preview or export maximum.
- Run the seeded app.
- Open SQL Editor.
- Select the sample sales data source.
- Run a simple query against the sample sales model.
- Use the result to validate the seeded dashboard metrics.
Analyzer and Dashboard Builder depend on trustworthy metadata and reusable SQL models. SQL Editor is the manual inspection path for checking those definitions before relying on AI-assisted answers or dashboards.