SQL Server Administration Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

The first hour on SQL Server

SQL Server is the engine in this window. You use the sqlcmd client or the admin tool you already have. The usual port is 1433. T-SQL is the dialect. Auth is Windows, or mixed, and you write which. This page is the planning habit for an admin who already chose it. It is not a vendor manual, and it is not a script you paste unread. The install generator drafts a starter. You read it. The tools do not log into a host.

The lab listens where this engine can be kept to yourself. The lab is reachable only from the machine you are using until a firewall story exists. Do not enable features such as a shell procedure to test the install. A generated file that publishes the service to every address is a file you edit before it runs. prompt-for-this is not a password. The real secret stays in the store, and it does not go in the ticket or in a compose file you commit.

One change after the lab answers a trivial read. A version upgrade, a new account, and a backup job are three windows. The backup guide owns the restore test. The configuration guide owns a later setting. This page stops when the lab name, the version, and a read you understand are written down.

SQL Server is not PostgreSQL and not MySQL. An edition limit is real. Write the edition the version command shows. You do not point the client at an instance you do not administer, and you do not load a customer extract to prove the install.

A lab you can name, a read you can explain

Install on a lab host or run the drafted compose only after you have read it. Bind it as this page requires. Set an admin secret through a prompt or the store. Connect with sqlcmd or the admin tool you already run. Read the version. Create a lab database or the equivalent SQL Server calls a database, with a name that is obviously a lab.

Create one account that is not the superuser, if this engine has that idea. Prove it can do one small read or write of invented rows, and that it cannot administer the instance. The security guide is the longer grant story. Here you only prove the split exists.

Read the version and edition. Create a lab database. Connect with an account that is not sa. If mixed mode is on, sa has a store-backed secret or it is disabled. You do not invent a famous password.

Copy the config the install left behind before you change it. If you change anything, change one line and read the value back from the engine. Then stop. The Kubernetes draft, if you have one, is a later ticket. A cluster you have not backed up is not the first place a manifest runs.

# SQL Server lab. Review before you paste.
# The lab is reachable only from the machine you are using until a firewall story exists. Do not enable features such as a shell procedure to test the install.
# Client: sqlcmd or the admin tool you already run.
# prompt-for-this is not a password to keep or commit.
# Invent the rows. Do not load a customer extract.
# Copy the config before you edit it.
# A second session stays open across a restart.

A change you can finish

Production is a later canary of the same version and the same bind decision. This window is the lab proof.

Rollback is the lab you can throw away, or the previous config file you copied. You do not roll back by deleting a data directory you have not backed up.

Read the drafted install. Delete any bind to every address.
Start the lab and read the version with sqlcmd or the admin tool you already run.
Create an obviously named lab database.
Store the secret outside the ticket.
Prove a narrow account, or write that this engine's equivalent is still open.
Copy the config. Change at most one line.
Hand backup, grants, and the next node to their guides.

Mistakes that outlive the command

SQL Server fails in the same few ways. Each one looks finished on the day you type it. The list is here so the ticket can forbid them before the window, not so you can recognise them in an incident review.

Pasting an install draft you did not read.
A password in the compose file or the ticket.
Listening on every address.
The application using the superuser.
A customer extract as the first data.
Deleting a data directory as a reset.
Treating SQL Server as a different engine you already know.
A second product installed in the same hour.
No version written down.
A restart from the only session.
Enabling extra surface area so a sample script would run.
Calling the lab a backed-up production instance.

Decisions to write down before the window

One decision for SQL Server: The host is a lab you administer. The version was read from the engine, not from the draft. The bind matches this page. The secret is not in the ticket. The lab name is obvious. Invented rows were enough for the proof. A narrow account was proven, or the gap is written. The config was copied before any edit. At most one setting changed. Backup is the next guide, not a feeling. The auth mode and the edition are in the ticket. And a second person can say what SQL Server is for on this host.

The hour you stop

Write the database name, the host, and the clock time before you change anything for SQL Server. If this database is serving people and you do not have a copy, this hour is a plan. A plan you can read tomorrow is a success. A change you cannot undo is not.

Use a lab or a restored copy. The rows you read are rows you are allowed to hold. You do not point a client at a database, a cluster, or an account you do not administer. The tools on this site run in the browser. They do not log in, and they do not scan.

prompt-for-this is a reminder that a secret is missing. It is not a password, a token, or a key you save. The real secret stays in the password store. If a connection string, a log, or a ticket still contains a live secret, stop and rotate it. Then delete the copy.

One change. A config line, an index, a grant, and a restore do not share a window. If two things move and the outcome is wrong, you will not know which one did it. The rollback is the previous file or the backup you already tested.

A second person reads the scope aloud: which host, which database, which account. If they cannot find it in the ticket, the ticket is not ready. Silence is not agreement.

The lab listens on localhost. 127.0.0.1 is the address you bind until a firewall story exists. example.com is not your host. A generated file that listens on every address is a file you edit before it runs.

Do not run a statement you cannot undo. A delete or a drop without a backup and a where-clause you have read is the mistake this page is here to prevent. Read the statement. Count the rows it will touch. Then decide.

Keep the previous config and the previous dump. A generator draft is not the previous file. The previous file is what you put back if the new one is wrong. You practised the reload with a second session open when the change can lock you out.

If a step fails twice, stop. The failure is the result. Adding a command from a forum beside a half-applied config produces a database nobody can explain. Rebuild the lab from the copy you kept.

When the checks pass, the next database waits until someone else can repeat the proof from the notes. SQL Server is done for this window when the proof is written, not when the client printed a prompt.

This page is a planning guide. It is not a vendor manual, not an official standard, and not legal advice. If an auditor must see the decision, they see the ticket and the evidence, not this paragraph.

Hand the finished note to the neighbouring guide that owns the next step, and leave this database alone until that guide has its own window.

SQL Server checks before a second instance

Confirm this before you call the change done: The version command output is in the ticket. The lab name is obvious. A trivial read of invented rows worked. No password is in the ticket or the compose file. The service is not bound to every address. The previous config exists if you edited one. You did not load customer data. A second session exists if you restarted. The hostname in the prompt matches the hostname in the ticket for SQL Server. The result line includes the time and the person, not only the command. You can point at the rollback value without searching a chat history. And done is a sentence a second person can repeat: the proof for SQL Server happened, and the next host is not started early. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar.