Skip to content

Reusable SQL for the whole team

Stop rewriting
the same useful query.

Save useful SQL, rerun it against its connection, and return to past results. Share the specific run your teammate needs to see.

Open your query librarySee the preview

Choose a connection to find its saved queries.

Sharing exposes a specific run result, not live query access.

A closer look at Saved Queries.

Product preview · Sample data
Illustrative interface

Platform capability

Saved Queries

Northstar Postgres / saved query

Monthly revenue by region

RUNS
14
LAST RUN
2 hours ago

Query

SELECT
  region,
  SUM(amount) AS revenue,
  COUNT(*) AS orders
FROM public.orders
WHERE created_at >= date_trunc('month', now())
GROUP BY region
ORDER BY revenue DESC;

Most recent run result

Illustrative values

  • North America

    REVENUE
    Illustrative $1,248,320
    ORDERS
    8,412

  • Europe

    REVENUE
    Illustrative $843,100
    ORDERS
    5,891

  • Asia Pacific

    REVENUE
    Illustrative $612,750
    ORDERS
    4,203

Illustrative result -- data controls disabled

Why Saved Queries

Useful SQL, ready for the next question.

01

Save it where it belongs.

Keep named queries with their team connection, ready to open and run again.

A library for each connection

02

See what it returned.

Review recorded runs, results, timing, and status when a number or failure needs explaining.

Run history with context

03

Share the answer.

Send a specific run result to a teammate without granting live query access through the link.

A link to a point-in-time result

Practice the underlying skill

Work through a SQL example.

Before a query becomes a shared reference, make its grain explicit. Learn why two one-to-many joins can inflate a total and how to check the result.

Runs locally in DuckDB. Fictional data. No signup required.

Save the work that deserves a second run

Name a useful query and keep it under its connection. The next time the same question comes up, open the SQL, adjust it if needed, and run it again.

The run history keeps the outcome in context: when it ran, how long it took, its status, and the available result. Share a completed run when someone needs the evidence behind a number.

Saved queries / run history

Every execution logged. Any run shareable.

Illustrative run history

Each run records the timestamp, duration, row count, and status. Select a completed run to generate a share link that exposes the result, not the live connection.

Sample data -- no live execution

Query: Monthly revenue by region

5 runs shown

  • run_0047

    2026-09-02 14:32 UTC

    completed
    DURATION
    1.8s
    ROWS
    3

  • run_0046

    2026-09-01 09:15 UTC

    completed
    DURATION
    2.1s
    ROWS
    3

    Shareable link (illustrative)

    https://data.synehq.com/share/run_0046

    View this run's result only. No live query access.

  • run_0045

    2026-08-29 16:48 UTC

    failed
    DURATION
    0.4s
    ROWS
    0

  • run_0044

    2026-08-28 11:02 UTC

    completed
    DURATION
    1.6s
    ROWS
    3

  • run_0043

    2026-08-25 08:30 UTC

    completed
    DURATION
    1.9s
    ROWS
    4

Run logging

Every execution is recorded regardless of outcome. Failed runs include the same metadata so you know when and why something broke.

Share scope

A share link exposes one run's result. The recipient cannot re-run the query or access the connection.

Before you get started

A few useful answers.

Talk through your use case
Where are saved queries stored?

Each saved query belongs to a team connection. Open that connection to find, edit, and rerun its saved SQL.

What can I see in run history?

Recorded runs include the time, duration, row count, status, and available result. Use the history to inspect an earlier outcome or investigate a failed run.

Does a shared link give live database access?

No. It exposes a particular run’s result and its query context. The recipient cannot use that link to open the console or rerun the query against the live connection.

Keep the queries your team keeps asking for.

Save the SQL once, return to its run history, and share the result that answers the question.

Open your query libraryOr book a product walkthrough