Skip to main content

Caring for the ScrewDrivers Database

In the first deployment tutorial, the ScrewDrivers Database installer created your database and you moved on. That's fine for day one — but everything your deployment knows lives in that database, and the upgrade guide's rollback plan is literally "restore your backup." This tutorial makes you comfortable operating it: you'll look inside, set up scheduled backups, prove you can restore, and learn the health checks worth repeating.

You'll need: your first deployment finished, SQL Server Management Studio (SSMS), and an account with administrative access to the SQL Server. About 45 minutes.

Step 1: Look inside​

Open SSMS, connect to your SQL Server, and expand Databases → ScrewDrivers (or your custom name). Expand Tables — this is your entire configuration: printers, owners, assignments, profiles, and reporting data.

Two things worth internalizing:

  • You never edit these tables directly. ScrewDrivers Administration is the interface; the ScrewDrivers Database installer is the only thing that changes the schema (once per upgrade).
  • Size: right-click the database → Properties → note the current size. A new deployment is small; reporting data drives growth over time.

Checkpoint: you can see the ScrewDrivers database and its tables, and you know its current size.

Step 2: Take a manual backup​

Right-click the database → Tasks → Back Up… Confirm Backup type: Full, note the destination path, and click OK. Seconds later you have a .bak file — your rollback plan for upgrades and your recovery from anything else.

Checkpoint: a full backup completed and you know where the .bak file landed.

Step 3: Schedule it​

A backup you have to remember isn't a plan. In SSMS, under SQL Server Agent → Jobs, create a job that runs a full backup on a schedule matching how often your configuration changes — nightly is a sensible default. On SQL Express, SQL Server Agent isn't available; schedule sqlcmd with Windows Task Scheduler instead:

sqlcmd -S SERVERNAME\SQLEXPRESS -Q "BACKUP DATABASE ScrewDrivers TO DISK='D:\Backups\ScrewDrivers.bak' WITH INIT"

While you're here, check the recovery model (Properties → Options): Simple suits most ScrewDrivers deployments — configuration changes at human speed, and Simple keeps the transaction log from growing unbounded. Use Full recovery only if your organization's DBA standards require point-in-time restore.

Checkpoint: backups happen without you, and you know your recovery model.

Step 4: Prove you can restore​

An untested backup is a hope. Restore the .bak from Step 2 as a new database: right-click Databases → Restore Database…, select your backup file, and under Files and Options rename the target to ScrewDrivers_RestoreTest so you don't touch the real one. Confirm it restores cleanly, glance at its tables, then delete ScrewDrivers_RestoreTest.

If you ever restore for real — a failed upgrade, a corrupted database — the flow is the same, restoring over the original name after stopping ScrewDrivers services, then reinstalling the matching product version.

Checkpoint: you have personally restored a ScrewDrivers backup and seen it work.

Step 5: The recurring health checks​

Put these on your calendar — monthly is plenty for most environments:

  1. Backups are still running and the newest .bak is recent.
  2. Database size trend — steady growth is normal; a sudden jump usually means reporting volume changed.
  3. Disk headroom on the SQL data and backup volumes.
  4. Before each ScrewDrivers upgrade: a fresh backup, per the upgrade guide.

What you've learned​

You can find, back up, restore, and monitor the database your deployment depends on — which means upgrades have a real rollback and surprises have a recovery path.

Where next: connection details change someday? Changing SQL Access Data After Your Install. Locking down permissions? Database credentials and authentication. High availability? SQL Always On Compatibility. Continue the path with Mastering ScrewDrivers Administration.