DataPilot

Guide

Use threaded comments to document SQL decisions

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.

Screenshot placeholder

Add screenshot: query tab showing a comment thread, mention UI, and a resolved / open state.

Screenshot needed

Screenshot needed: query tab with comment thread, mention UI, and resolved/open states.

Sizes: 1600x900 hero + OG 1200x630; Alt: "Threaded SQL query comments inside the DataPilot workspace".

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.

Screenshot placeholder

Add screenshot: history drawer showing runs with timestamps and a “download export” action next to a run.

Screenshot needed

Screenshot needed: history drawer showing runs with timestamps, versions, and download actions.

Sizes: 1600x900 hero + OG 1200x630; Alt: "Run history and versions with context for exported files".

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