Skip to content
Shared SQL query library

A shared SQL query library the team will actually use.

The diagnostic query that fixed last month outage. The reconciliation query the back-office runs every day. The cleanup probe nobody remembers who wrote. Save them once. Run them through the agent. Audit every execution.

Shared SQL query library with folders, saved queries, variables panel, and audit log
Organize

Folders by domain

Reconciliation, finance, support, on-call. A folder per topic, queries with descriptions, the team finds what they need.

Reuse

Variables for the bits that change

Typed variables (string, number, date, datetime, json, guid, boolean) with defaults at the query level and overrides per user.

History

Versioning per query

Every save is a checkpoint. Restore a previous version. Read the diff. Understand who changed what when.

Run safely

Read-only via agent

Statement classifier rejects DML and DDL. Use a read-only database role. The agent enforces statement timeouts.

Audit

Every run is a row

Rendered SQL, variables applied, who, when, on which connection, row count, duration. Compliance and post-mortems happy.

Schedule

One click to a recurring export

A saved query becomes a schedule that delivers CSV or Excel to email or Slack. The recurring extract automates itself.

Why teams move off the alternatives

The places SQL hides today.

pgAdmin and DBeaver tabs

Personal. Lost on laptop reset. Cannot be shared without copy-paste. No execution audit.

GitHub gists

Shared but disconnected from the database. No variables. No execution. Half the time the gist is private.

Slack threads

Searchable for two weeks then buried. The link to the message dies when the channel rotates. No variables, no audit.

Notebooks and dashboards

Heavyweight for an operational query. Often want cloud DB access. Not the right tool for a quick reconciliation extract.

FAQ

Shared SQL query library for teams

Can the team see and edit queries together? +

Yes. Save a query under the company scope and the team sees it. Personal scope keeps it private. Versioning means edits are not destructive.

Are variables required? +

Optional. Plain SQL works. When a query needs a customer id or a date range, mark it as a variable and the runner prompts for it. Defaults at the query level, overrides per user.

Can I run write queries? +

No. DML and DDL are rejected before dispatch. Use a read-only database role for the connection. To write to the database, use a migration tool and let Taavik observe the result.

Move it in

Save the first query the team keeps re-writing.

Free forever for personal use, Pro for shared workspaces and unlimited library size.