AsBuilt

Your database,
as built.

AsBuilt pushes your SQL Server schema to a private GitHub repository, right from SSMS. One file per object, and a new commit only when something actually changed.

Download for SSMS 21 and 22 See what lands in your repo

Free. Windows only. Schema only, never your data.

An as-built drawing of the dbo.Order table The table is drawn with its columns. The new qty column is circled in red and marked revision 2. The title block lists two revisions: the initial snapshot and the added qty column. dbo.Order id int PK customer_id int FK ordered_at datetime2 status tinyint qty int not null dbo.Customer idPK name 2 Rev Description Date 1Initial snapshot2026-10-02 2Added qty to dbo.Order2026-10-30 SheetTables/dbo.Order.sql ProjectSales Drawn byAsBuilt

Three clicks to a commit

No local clone, no Git client to install, nothing to configure first. Sign in to GitHub once and AsBuilt remembers where each database goes.

  1. Right-click the database

    In Object Explorer, choose Push schema to GitHub. It is also under Tools > AsBuilt.

  2. Pick a repository

    Your account or one of your organizations. If the repository does not exist yet, AsBuilt creates it as private.

  3. Get a commit of what changed

    Every object is scripted and compared with what is already there. New, changed and dropped objects go into one commit. Nothing changed means no commit.

Laid out the way you would look for it

One file per object, in a folder per object type. Tables carry their keys, constraints, indexes and triggers in the same file, so a pull request reads like a change to that table.

Scripts are written the same way every time: no generated timestamps, no machine-specific constraint names, consistent line endings. When the history shows a diff, something in the database really changed.

Your README, docs and CI files are left alone. AsBuilt only manages the folders it creates, so several databases can share one repository, each in its own folder.

sales-schema/
  README.md                yours, never touched
  Schemas/
  Tables/
    dbo.Customer.sql
    dbo.Order.sql          modified
  Views/
    dbo.vOpenOrders.sql
  StoredProcedures/
    dbo.usp_ShipOrder.sql  added
  Functions/
  Types/
  Synonyms/
  Sequences/

The rules it keeps

A schema says a lot about a business. AsBuilt is careful about where it sends one.

New repositories are private
Always. There is no setting that changes it.
Public repositories need your say-so
Pushing into an existing public repository stops and asks before anything is sent.
It never reads your data
Only object definitions are scripted. AsBuilt never changes your database either.
Your sign-in stays on your PC
The GitHub token is encrypted for your Windows account. Nothing is sent to Solvelop.
An empty result pushes nothing
If scripting comes back empty, AsBuilt refuses to commit rather than clearing out the repository.
Nothing is dropped silently
Objects it cannot script, such as procedures created WITH ENCRYPTION, are listed in the commit message and in SSMS.

Also on the command line

The installer can add asbuilt to your PATH. It runs the same engine without SSMS, so you can keep a repository current from a SQL Agent job or a scheduled task, and see what would change with --dry-run before pushing.

# sign in once
asbuilt login

# push, creating the private repo if needed
asbuilt push --server SQL01 --database Sales ^
  --repo solvelop/sales-schema

# preview only
asbuilt push --server SQL01 --database Sales ^
  --repo solvelop/sales-schema --dry-run

Questions

What do I need?

Windows, SQL Server Management Studio 21 or 22, and a GitHub account. Any SQL Server version that SSMS can connect to will work.

Is it really free?

Yes. No account with us, no trial, no upgrade prompts.

Does Microsoft support SSMS extensions?

Not officially. SSMS 21 and 22 load extensions, but Microsoft does not support them. AsBuilt only adds menu items and does its work in the background, and the Tools menu keeps working even if a future SSMS changes Object Explorer.

What about logins and Agent jobs?

Not yet. AsBuilt scripts what lives inside a database. Users, roles and permissions are optional; server-level objects are out of scope for now.

Does it work with GitHub organizations?

Yes. Pick the organization as the owner. If the organization restricts third-party apps, an owner approves AsBuilt once.

How do I uninstall it?

From Windows Settings > Apps, like any other program. The uninstaller removes the extension from every SSMS it was added to.

Start a history of your schema today

The first push records the database as it stands. Every push after that shows exactly what changed.

Download for SSMS 21 and 22

Version 1.0.0. Requires Windows and SSMS 21 or 22.