Quick search for SQL Server Management Studio.
Find any table, view, stored procedure, or function in any database.
Type three letters. Hit Enter. Done.

Features • Shortcuts • Install • Build • Docs

SQL Hunting Dog was the gold-standard quick-search add-in for SSMS for years — and it has been abandoned since 2018. It only runs on SSMS 2008–2014 (32-bit, .NET 3.5), and Microsoft never shipped a first-party equivalent. SSMS's native "Find Objects" dialog is modal, slow, and forces you to click through Object Explorer trees one node at a time.

SQL Pilot is a modern, from-scratch replacement. Same fast workflow, all the same context actions, runs on SSMS 18, 20, and 22 — including 64-bit SSMS 22 on both x64 and Arm64. The default keybindings, the type-aware action set, and the muscle memory all match hunting-dog so you can switch without retraining.

• Fuzzy search across every database on every connected server. Indexes tables, views, stored procedures, scalar and table-valued functions, and synonyms.
• Search scope — the filter button (funnel icon, Alt+S) opens a checkbox tree of your connected servers and their databases. Uncheck what you don't care about and it drops out of search and stops being indexed; exclusions persist across SSMS restarts. Everything is in scope until you say otherwise, and new databases on an in-scope server are picked up automatically.
• Keyboard-driven — type to filter, arrows to navigate, Enter to act, Right for the secondary action, Space for the context menu. No mouse needed.
• Type-aware context actions — Select Top N, Edit Top N (the real editable grid, not a SELECT script), Design Table, Script Create, Modify, Execute. Tables get Edit Data. Procedures and functions get Execute. Views get Modify View.
• Favorites — pin objects you use constantly, persisted across SSMS restarts.
• Recent objects — automatically tracks your most recently accessed objects per session.
• Azure SQL Database — full support, including the URN domain stripping, USE [db] rejection, and 3-part-name restrictions that SSMS doesn't tell you about.
• Friendly one-click installer — branded WPF installer that detects every SSMS version on your machine, lets you pick which to install into via checkboxes, downloads the matching release ZIP from GitHub itself, and verifies SHA-256 before extracting. Same exe handles uninstall. PowerShell scripts also ship for CI / scripted deploys.
• Auto-updater — checks GitHub once a day in the background, never auto-installs, remembers skipped versions, and stays out of your way if you're offline.
• Theme aware — follows SSMS dark/light theme.

1. Download SqlPilotInstaller-vX.Y.Z.zip from Releases
2. Extract anywhere and run SqlPilotInstaller.exe
3. Approve the UAC prompt
4. Pick which SSMS versions to install into (the installer detects what you have), click Install
5. Restart SSMS · Press Ctrl+D to open SQL Pilot

The installer downloads the matching release payload from GitHub itself, verifies it, and copies the extension into every selected SSMS version. Same exe handles uninstall — re-run it on a machine where SQL Pilot is already installed and the Uninstall button appears.

First run will show "Windows protected your PC" because we don't pay for an EV code-signing certificate yet. Click More info → Run anyway. The installer source is in src/SqlPilot.Installer/ — verify before running if you want.

SSMS 22 users can also install from the VSIX Gallery or SSMS Gallery: download the .vsix and run it (or subscribe to the gallery feed for update notifications). SSMS 18 and 20 must use the installer above — the .vsix targets the modern shell (SSMS 21–22) only.

For CI pipelines, silent installs, or admins who script everything:

1. Download SqlPilot-vX.Y.Z.zip from Releases
2. Extract it somewhere
3. Run as administrator:

   powershell -ExecutionPolicy Bypass -File Install-SqlPilot.ps1

   The script detects every SSMS version on your machine (18, 20, and/or 22) and installs into each one. Caches are invalidated automatically.
4. Restart SSMS
5. Press Ctrl+D to open SQL Pilot

powershell -ExecutionPolicy Bypass -File Uninstall-SqlPilot.ps1

Removes SQL Pilot from every SSMS version it's installed in. Per-version errors don't abort the others — if SSMS 20 is locked because it's still running, the uninstaller still cleans up 18 and 22 and tells you what to retry.

• Visual Studio 2022 with the ".NET desktop development" and "Visual Studio extension development" workloads
• .NET Framework 4.7.2 targeting pack
• SSMS 18, 20, or 22 installed locally (the projects reference SMO DLLs from the SSMS install — see lib/Ssms18/ and lib/Ssms22/)

nuget restore SqlPilot.sln
msbuild SqlPilot.sln /p:Configuration=Release /p:Platform="Any CPU"

dotnet test tests/SqlPilot.Core.Tests/SqlPilot.Core.Tests.csproj --configuration Release

# As administrator
.\build\Deploy-Dev.ps1 -Version 22   # or 18 / 20

Single AnyCPU build. Works on Windows x64 and Arm64. No native dependencies.

src/
├── SqlPilot.Core/             # Search engine, models, favorites, recents, scope (no SSMS deps)
├── SqlPilot.Smo/              # SMO database object provider (SSMS 22 SMO 18.x)
├── SqlPilot.Smo.Legacy/       # Same source, references SSMS 18 SMO 16.x
├── SqlPilot.UI/               # WPF controls, view models, themes
├── SqlPilot.UI.Demo/          # Standalone WPF app for UI work without SSMS
├── SqlPilot.Package/          # SSMS 22 extension (VSSDK 17.x)
├── SqlPilot.Package.Legacy/   # SSMS 18/20 extension (VSSDK 15.x)
└── SqlPilot.Installer/        # Standalone WPF installer .exe (downloads from GitHub Releases)

Two extension builds from one source tree, sharing every file except the VSSDK references and the manifest schema. The installer is a separate WPF exe that lives outside the extension load chain. See docs/ARCHITECTURE.md for the full breakdown.

Contributions welcome. The code is intentionally small and easy to navigate — read docs/ARCHITECTURE.md and docs/SSMS_INTEGRATION_NOTES.md before touching the SSMS integration layer (there are several non-obvious gotchas documented there).

1. Fork the repo
2. Create a feature branch
3. Make your changes — keep PRs focused
4. Run dotnet test tests/SqlPilot.Core.Tests/SqlPilot.Core.Tests.csproj
5. Open a pull request

SQL Pilot was inspired by SQL Hunting Dog, the pioneering quick-search add-in for SSMS by Alexander Maslyukov and Maxim Novikov, with contributions from pstraszak, FastNinja, and pklejnowski.

SQL Pilot is an independent from-scratch implementation — no code is copied — but the workflow, default keybindings, and type-aware action set are deliberate matches so hunting-dog users can switch without retraining.

Licensed under the Apache License, Version 2.0. See NOTICE for additional attribution.