Saved Queries

Saved Queries turn useful SQL into reusable analysis. They are best for queries you expect to run again or share with teammates.

What You Can Save

• Reusable reports.
• Operational checks.
• Debugging queries.
• Chart-ready SQL.
• Queries generated or improved with AI after manual review.

When to Save

• The same question comes up repeatedly.
• The query contains non-obvious business logic.
• A teammate may need to reuse it.
• The result powers a recurring chart or workflow.

Naming Recommendations

Use names that describe the business question, not just the table name.

Good examples:

• Weekly active users by product area.
• Failed payments in the last 24 hours.
• Slow ClickHouse queries by user.

Usage Flow

1. Write and validate SQL.
2. Clean up formatting and remove temporary filters.
3. Add a clear name and description.
4. Save the query.
5. Revisit it periodically to keep assumptions current.

Team Practice

Document time ranges, filters, joins, and metric definitions so others can safely reuse the query.