Your database,
as built.
AsBuilt pushes your SQL Server schema, and the Agent jobs that go with it, to a private GitHub repository, right from SSMS. One file per object, and a new commit only when something actually changed.
Free. Windows only. Schema only, never your data.
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.
-
Right-click the database
In Object Explorer, choose Push schema to GitHub. It is also under Tools > AsBuilt.
-
Pick a repository and jobs
Choose one of your repositories from the list or type a new name, and AsBuilt creates it as private. Agent jobs with a step in the database are already checked.
-
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.
Or let it push while you work
Tick one box and AsBuilt pushes that database every 15 minutes, or whatever interval you set, for as long as SSMS is open. Close SSMS and it stops. There is no service and no scheduled task to manage.
- Commits only real changes
- Each run starts with one quick catalog query. If nothing changed, that is the whole run, and no commit is made.
- Quiet
- No pop-ups. The result shows in the SSMS status bar, and Tools > AsBuilt > Automatic pushes lists the last run for each database.
- Uses the connection you already have
- A database is pushed only while Object Explorer is connected to its server. Nothing new to store or sign in to.
- Never the risky choice
- Jobs flagged for passwords keep their last pushed version, and automatic pushes never go to a public repository.
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.
SQL Server Agent jobs live in msdb, not in the database, so you choose which ones belong with it. Each checked job is one file in AgentJobs/, and a disabled job or a moved schedule shows up in the history like any other change.
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/ AgentJobs/ Nightly Load.sql modified
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.
- Passwords in jobs get flagged
- Job steps with sqlcmd -P, connection string passwords, dtexec /DECRYPT or plain-text PowerShell secrets stop the push and ask. Skip is the default.
- Server secrets stay on the server
- Linked-server passwords and credential secrets become placeholders. SQL login password hashes are pushed only if you opt in, and the sa password never is.
- 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, # with the Agent jobs that run in Sales asbuilt push --server SQL01 --database Sales ^ --repo solvelop/sales-schema --agent-jobs auto # 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.
Which Agent jobs can I include?
Any job your login can see. Sysadmins and members of SQLAgentReaderRole see every job; other logins see only the jobs they own. Express and Azure SQL Database have no Agent, so the section does not appear there.
What about logins and linked servers?
Right-click the server instead of a database. That push covers logins, server roles, linked servers, credentials, server triggers, Agent operators, alerts and proxies, and sp_configure values. Passwords and secrets are never pushed. Login SIDs always are, so database users still match after a restore. Password hashes are off unless you turn them on.
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.
Version 1.0.12. Requires Windows and SSMS 21 or 22. Close SSMS before installing.
The installer is not code-signed yet, so Windows may say "Windows protected your PC." Choose More info, then Run anyway. On a managed work PC, IT may need to allow it.