How to organize snippets by database for database administrators

Learn how database administrators can organize snippets by database, with steps, tool options and common mistakes to avoid.

By SupaKeeper · 2026-11-04

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

Give each database its own folder, name each snippet for its task, and test the search before you rely on the list. The steps below cover the setup, and the tools section lists options with the facts their sources give.

Option	What it can do	What to check
Copilot AI Productivity Suite	Snippets can sit in nested folders, and you can bundle several into a group that is referenced all at once. ^[1]	Check whether the Free plan's 20 weekly insertions fit how your team works. ^[1]
Shared text file or notes app	A folder for each database, kept in a file or app your team already uses.	Check whether it can sort snippets by database and how it handles sharing.
Snippet features in your editor	Snippet features already built into your editor.	Check whether it can group snippets by database and whether the team can share them.

What you need before you start

Before you organize anything, decide which databases your snippets belong to. Most database administrators work with several environments, such as production, staging and a local copy, so list each one along with the kinds of queries that go with it.

Keep a short naming rule ready. A prefix that shows the database name and a second part that shows the task, such as backup, index review or user access, makes each snippet easy to find later.

Gather the snippets you already use, including the ones saved in scripts, notes and shared files. Seeing them together shows what needs sorting and what can be removed.

Check that you can read and edit the snippets, and find out who else on your team will use them. A list that only one person can change may not last.

Finally, pick where the sorted list will live. It can be a folder in your editor, a shared location or a tool built for snippets. Having these items ready makes the rest of the work faster and keeps the list usable after the first setup.

Step by step

List the databases your snippets serve, including each environment, such as production, staging and test.
Gather every snippet you already keep, from scripts, notes and shared files, and copy the ones you still use into one place.
Give each database its own folder. Keep the layout the same for every database so you always know where to look.
Name each snippet for the task it performs, such as checking table sizes or reviewing failed logins. When a snippet is used across databases, include a clear marker in its name.
Mark any values that change from one database to another with a placeholder, so the snippet asks for the right value each time it is used.
Put snippets that several databases share in a common group, and keep single-database snippets in their own folder.
Test the search by typing a database name and a task, then confirm the right snippet appears.
Share the layout with your team and agree on the naming rule, so new snippets follow the same pattern.
Review the list on a regular schedule, moving out snippets nobody uses and renaming any that are unclear.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site, SupaKeeper. It is a VS Code extension that needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. ^[1]

You install it from the VS Code Marketplace as LunarWerx.copilot-suite. ^[1] Snippets can sit in nested folders, and you can bundle several into a group that is referenced all at once. ^[1] Placeholders like ${name} or ${name:default} in a snippet ask you for a value when the snippet is inserted. ^[1]

You can select several snippets and move them, delete them or insert all their references at once. ^[1] You can export snippets as JSON or make a share link, and teammates can import it. ^[1]

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1]

While VS Code telemetry is on, it sends anonymous usage statistics, but never snippet content. ^[1] The extension uses a proprietary licence; the software is proprietary and confidential to LunarWerx. ^[1]

Other options include a shared text file or a notes app with a folder for each database, or the snippet features already built into your editor. Check whether each one can sort snippets by database, how it is shared with the team, and whether it works on the machines you use.

Common mistakes to avoid

Avoid keeping one long list of snippets with no folders, since a search for a single database then returns unrelated results.

Avoid vague names such as query1 or fix, which say nothing about the database or the task.

Avoid copying a snippet into each database folder, because a correction made in one copy will not reach the others.

Avoid storing passwords, connection strings or access keys inside a snippet that will be shared or exported.

Avoid skipping placeholders for values that change, because a snippet written for one database may run against the wrong one if its name is left in place.

Avoid building a layout that only you understand, since your team needs to find the same snippets.

Frequently asked questions

How can database administrators organize snippets by database?

Give each database its own folder and name each snippet for the task it performs, so a search for the database name or the task brings up the right one quickly. Check whether your tool supports nested folders and groups, since those let you sort by environment and then by database. Copilot AI Productivity Suite lets snippets sit in nested folders, and it lets you bundle several into a group that is referenced all at once. ^[1]

Can Copilot AI Productivity Suite ask for the database name each time a snippet is used?

Placeholders like ${name} or ${name:default} in a snippet ask you for a value when the snippet is inserted. ^[1] A single snippet can therefore serve several databases, with the database name supplied each time it is used. ^[1] Check that the placeholder names match the way your team writes database names, so the prompts are clear.

Does Copilot AI Productivity Suite work with Cursor or other editors?

It is a VS Code extension that needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. ^[1] You install it from the VS Code Marketplace as LunarWerx.copilot-suite. ^[1] Check that your editor is one of these before you plan your setup around it.

How much does Copilot AI Productivity Suite cost for a database team?

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1] Compare these limits with how often your team inserts snippets before choosing a plan, and check the plan details before you commit.

Does Copilot AI Productivity Suite send snippet content anywhere?

While VS Code telemetry is on, it sends anonymous usage statistics, but never snippet content. ^[1] Check your own editor telemetry setting and your team's policy on usage data before you share a snippet set. You can also export snippets as JSON or make a share link when you want teammates to import them. ^[1]

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1]

Try Copilot AI Productivity Suite

Sources

Copilot AI Productivity Suite's own description of itself (the product of this site's publisher)