Share SQL Queries Online

Stop sending SQL as screenshots, Slack snippets, and email attachments. SaturnSQL lets you share a query as a link (the SQL and its results together) and build a saved query library your whole team can search, run, and reuse: one governed home for the team’s query assets instead of scattered scratch files and snippets.

Copy-pasting SQL around has a familiar failure mode: the query in Slack drifts out of date, nobody knows which version is right, and the context (“why does this exclude trial accounts?”) gets lost in chat history. Three months later someone rewrites the same query from scratch, slightly differently, and now two dashboards disagree.

Sharing in SaturnSQL works differently because a query is a living object, not a text snippet. When you save a query, it gets a home: a place in the team's folder structure, a description for context, and version history so you can see how it evolved. Share the link and the recipient sees the current SQL and its output in the browser. No local client, no setup.

Three ways to share

Share the query itself. Send a teammate the link to a saved query. They can read it, run it against the shared connection, and adapt it for their own question, with the description and version history attached to the SQL instead of buried in a DM thread. This is the core of our collaborative SQL editor.

Share a report, not SQL. Every saved query also has a report page: filters at the top, the table underneath, export at the bottom, and no SQL in sight. For a founder or a customer success manager, that link is the right one to send — pair it with the viewer role and they can consume every shared report without being able to run anything else.

Share the results. For people who just need the numbers, export results as CSV or send them to Slack. The query stays in the workspace; the answer goes where the conversation is.

Share on a schedule. If someone asks for the same data every week, stop re-running it by hand. Schedule the query and push fresh results into Google Sheets automatically. Stakeholders get a spreadsheet that's always current.

From shared queries to a query library

The real payoff comes when sharing becomes the default. Once every useful query lands in the shared library, “do we have a query for X?” stops being a Slack archaeology project. New team members browse the library on day one and see how the team defines its metrics. The canonical version of “monthly active users” exists exactly once, and everyone references it.

Sharing queries online without making them public

“Online” does not mean “public.” A shared query link only works for people signed in to your workspace — anyone else gets a not-found page. Queries are private by default and shared with one explicit toggle, so nothing leaks by accident, and the database credentials behind the connection are never part of what gets shared. If you need to hand results to someone entirely outside the company, export the CSV or schedule the query into a Google Sheet you control the sharing of.

Common questions

How do I share a SQL query with someone? Save it and send the link. The recipient sees the SQL and its results in the browser, with no copy/paste, no screenshots, and no local database client.

Are shared queries public? No. Links are scoped to your workspace: teammates must be signed in, and everyone else gets a not-found page. Queries stay private until you explicitly share them.

Can I share results with people who don't have database access? Yes. Export to CSV, schedule into Google Sheets, or push to Slack. Stakeholders get the data without touching the database.

Do shared queries stay up to date? Yes. A shared query is a living object, not a snapshot. Improvements are visible to everyone, and version history tracks what changed.