In this article we will go over why there isn't a Saved Queries feature in superQuery, and why categorizing your queries into Boards is a much better alternative.
Before we go over why superQuery doesn't have a Saved Queries feature, it's important to go over why this feature exists in Google BigQuery in the first place.
Queries don't persist in BigQuery
When you refresh a page running Google BigQuery, any SQL you had written in your query editor will disappear.
Because queries don't persist in BigQuery over time, Google offers the "Saved Queries" feature for you to quickly access queries you use frequently — or perhaps just don't want to rewrite again.
Now let's explore why you don't need Saved Queries in superQuery
Queries DO persist in superQuery Tabs
Whether you execute a query or your query is a work-in-progress, the SQL will always be saved in its tab.
The only way a query will disappear is if you erase it yourself, or delete the tab it's stored in.
How do you organize and store multiple queries?
Moreover, instead of having a single Saved Queries folder, you have multiple Boards in superQuery.
Think of boards as workspaces for grouping related queries together and categorizing them.
You could have one board with three queries dedicated to Website Analytics, and another board containing queries for Marketing Campaigns, as illustrated below.
From the perspective of organization, this is a much better alternative than having a single list of 40+ unrelated queries.
What about private and project-level saved queries?
By default, all of your queries and boards are private.
If you'd like to share your board(s) with others — our equivalent of project-level queries — you can do so in three clicks.
When you share access to a board, users will not be able to edit the SQL of your queries — SQL for tabs you can't edit will be faded.
Shared users can do the following in your board:
- View the SQL of the queries.
- Copy the SQL and paste it into their own board.
- Access the dashboard view of your board.
- Modify your variable(s) values if they exist and refresh the dashboard — any query affected by the changed value will be charged to the billing project of the board admin.