Guide

Use threaded comments to document SQL decisions

Q: What are SQL query comments used for?

Query comments capture context like decisions, approvals, and edge cases. They stay attached to the SQL so teams can review and trust exports later.

Q: Do comments stay linked to runs and exports?

Yes. Comments remain visible alongside run history and versions, so you can trace why a query changed and which CSV/Excel export was produced.

Q: Can I use comments in a collaborative SQL workflow?

Yes. Threaded comments support mentions and handoffs so teams can collaborate without moving context into external docs.

Keep discussions attached to the query that matters. Comments stay visible next to versions and run history, so exports don’t lose context when they get shared.

Start free No credit card required. See the query workspace

Tip: Pair comments with version history so reviewers can restore past SQL and re-run the exact export when needed.

Threaded comments in the editor

Use threads to capture questions, approvals, edge cases, and “why we changed it” notes right where the SQL lives. Before you export results, you can scan the thread to confirm assumptions and reduce rework.

Size: 1600x900 (retina) - crop to 1200x630 for OG.

Keep comments linked to run history

When a query evolves, you still need a trustworthy trail. Comments remain visible alongside run history and versions, so you can trace what changed, when it ran, and which export was produced.

Size: 1600x900 (retina) - crop to 1200x630 for OG.

Share context with the team

Mention teammates, leave handoff notes, and keep review decisions in one place. When a schedule runs later, the same query context is still there-helping the team trust the exported CSV / Excel file.

Query workspace Scheduled exports