SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01recondoes a SQL Server instance already exist? (MSSQLSERVER = default, MSSQL$SQLEXPRESS = Express)
- 02reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
- 03reconavailable package managers: winget (real path, often off PATH under SYSTEM), choco, and the account running commands
- 04recon≥ 6 GB free and ≥ 4 GB RAM; port 1433 already taken?
- 05actInstall SQL Server ${edition}verify
- 06actGrant sysadmin to local Administratorsverify
- 07actCheck the connectionverify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall SQL Server ${edition}Verified by
Get-Service -Name 'MSSQLSERVER','MSSQL$SQLEXPRESS' -ErrorAction SilentlyContinue | Select-Object Name,Status - 02verifyGrant sysadmin to local AdministratorsVerified by
$g = (New-Object Security.Principal.SecurityIdentifier 'S-1-5-32-544').Translate([Security.Principal.NTAccount]).Value; $c = New-Object System.Data.SqlClient.SqlConnection 'Server=localhost;Integrated Security=True'; $c.Open(); $q = $c.CreateCommand(); $q.CommandText = "SELECT IS_SRVROLEMEMBER('sysadmin', N'$g')"; $q.ExecuteScalar(); $c.Close() - 03verifyCheck the connectionVerified by
$c = New-Object System.Data.SqlClient.SqlConnection 'Server=localhost;Integrated Security=True'; $c.Open(); $c.ServerVersion; $c.Close()
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never overwrite an existing instance or database. Windows authentication only: do not enable the SA account and put no password in clear text. Do not enable TCP/1433 or a firewall rule. The Developer edition is not allowed in production.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${edition} | Edition |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain SQL Server or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.07
More database recipes
- 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
- 02MySQLMySQL Server, secured, bound to localhost, started and verified.
- 03MariaDBMariaDB, secured, bound to localhost, started and verified.
- 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
- 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.