liveBook · Manning

SQL Server installation

As explained in 100 SQL Server Mistakes and How to Avoid Them

A SQL Server installation is the process of deploying and configuring SQL Server software and its selected components on a host environment.

Mistake 1: treating installation as a one-time manual build. Rushed DBAs can skip runbook steps, producing inconsistent instances and consuming time that could support higher-value work. section 8.0 section 8.8

A gold image fixes some consistency problems but can force every instance into the same edition or workload configuration. That is costly when environments mix Enterprise, Standard, Developer, OLTP, and data-warehouse needs. section 8.8

Prefer a parameterized scripted installation that can:

  • Select the SQL Server edition and instance name for the deployment. section 8.0 section 8.8
  • Supply service-account and sa-account settings without maintaining multiple gold images. section 8.8
  • Run smoke tests, configure the instance, and apply baseline hardening such as disabling remote access and renaming sa. section 8.8

Run a reusable installation

A PowerShell script can accept deployment-specific values instead of embedding one fixed build: ./InstallSQLServer.ps1 -SqlServiceAccount 'sqlServiceAccount' -SqlServiceAccountPassword 'Pa$$w0rd' -AgentServiceAccount 'sqlServiceAccount' -AgentServiceAccountPassword 'Pa$$w0rd' -SaName 'SQLAdmin' -SaPassword 'Pa££w0rd' -Edition 'Developer'.

How 100 SQL Server Mistakes and How to Avoid Them covers it

How deep it goes
Works from edition and naming choices through scripted configuration, smoke tests, and limited initial hardening.
Examples
Uses PowerShell listings that parameterize service accounts, edition, instance name, sa settings, module installation, and execution.
What it assumes
Assumes basic DBA deployment responsibility while teaching installation choices, scripting alternatives, and selected hardening steps.
What you can do after
Build it from scratch with a reusable PowerShell script that installs, smoke-tests, configures, and initially hardens an instance.
How it connects
Connects SQL Server installation with PowerShell, gold images, SQL Server editions, OLTP, data warehouses, and security hardening.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.