Preparing Windows Server for SQL Server means resolving compatibility, storage, identity, security and recovery decisions before running Setup. Meeting the database engine's minimum installation requirements is only the starting point. A server can pass Setup rules and still have unsuitable storage latency, no usable backup destination or an application dependency on an unsupported SQL release.
This guide prepares a standalone database host. Failover cluster instances, availability groups, replication and other high-availability designs have additional infrastructure requirements and should use their own implementation plan. The examples use illustrative host and path names; they are planning examples rather than a recommended capacity for every database.
Choose a supported SQL Server and Windows combination
Record the exact SQL Server major release, edition and intended servicing level. Match them to Microsoft's current Windows compatibility matrix and the application's certification. Windows Server 2025 does not support every older SQL Server release: current Microsoft guidance lists SQL Server 2019, 2022 and 2025 combinations, while older releases can be unsupported on that OS.
Check the required cumulative updates and prerequisites for the selected SQL version. Do not infer compatibility from another SQL release with a similar installer. Review features separately: the Database Engine, PolyBase, Analysis Services and other components can have different requirements. Install only features that have an owner and a business use.
Confirm licensing before choosing an edition. Developer edition is intended for nonproduction development and test scenarios; evaluation media has a time limit. Technical success with evaluation media does not establish a sustainable production deployment. Keep the approved media, product channel and upgrade method in the build record.
Size the workload rather than copying installation minimums
Estimate database size, growth, transaction-log generation, concurrent activity and the working set. Include backup and restore windows, maintenance jobs and reporting peaks. A small database can still be demanding if it performs frequent writes or expensive queries, while a large archival database may have different needs.
For a virtual server, discuss CPU scheduling, memory reservations or contention, storage performance and host backup behavior with the platform owner. Assigning more virtual CPUs is not always a remedy for slow queries. Avoid sizing the server solely from a vendor's minimum RAM figure or an arbitrary CPU-to-database-size ratio.
Document the initial SQL memory plan, leaving capacity for Windows, agents, backups and other required components. SQL Server's maximum memory setting is configured after installation, but its budget should be agreed beforehand. An unbounded engine on a small shared server can starve the operating system even though Setup completed successfully.
Prepare the server identity and operating system
Set the final computer name, join the intended domain if required and verify DNS and time. Apply approved Windows updates and complete pending restarts. Collect a baseline:
Get-ComputerInfo | Select-Object WindowsProductName,OsBuildNumber,CsName
Get-CimInstance Win32_ComputerSystem | Select-Object TotalPhysicalMemory,Domain
Get-Volume | Select-Object DriveLetter,FileSystem,SizeRemaining,Size
Get-NetIPConfiguration
Prefer a dedicated member server rather than installing the database engine on a domain controller. The domain-controller role creates security and operational constraints and complicates future role changes. Do not promote or demote a SQL host casually after installation; Microsoft's role limitations must be respected.
Confirm endpoint protection, monitoring, backup agents and their support for the chosen OS and SQL release. Any exclusions should follow current product guidance and the organization's security approval process. Disabling scanning across every data volume without review exposes more than the database workload requires.
Plan data, logs, tempdb and backups
Define directories for user database files, transaction logs, tempdb and backups. Separating paths helps management and capacity monitoring, but different drive letters on the same underlying storage do not guarantee separate performance or failure domains. Ask the storage owner what each volume actually provides.
Size for normal growth and temporary operations such as index maintenance and restore. Avoid placing production files on an administrator's profile or an unmanaged temporary volume. Confirm whether any cloud or virtual platform disk is ephemeral before storing database data there. Choose a supported filesystem and storage configuration appropriate to the SQL release and workload.
Place backups somewhere that survives loss of the database host. A local backup folder can be a staging location, but a backup existing only on the same failed volume is not a recovery strategy. Define off-host retention, encryption, access control and restore testing before the first production database arrives.
Choose service identities and administrative access
Use supported, dedicated identities for the engine and SQL Server Agent. Virtual accounts or gMSAs may be appropriate depending on the deployment and network access requirements. Confirm vendor support and required permissions. Do not use a personal administrator account whose password changes or departure can stop the service.
Prepare the groups that will administer the SQL instance, separating server administration from application access. Decide the authentication mode and avoid enabling SQL authentication merely because an application installer offers a convenient default. If SQL logins are required, manage their secrets through the approved process and grant application-specific rights.
Discuss instant file initialization and the Perform volume maintenance tasks right with the database and security owners. Its behavior and applicability depend on file type and SQL version; it is not a blanket permission to grant every service identity. Let SQL Setup configure service permissions through its supported mechanisms instead of manually rewriting folder ACLs afterward.
Decide names, ports and TLS before opening the firewall
Choose the instance name and client connection name. For a remotely accessed instance, decide whether it uses a fixed TCP port and whether SQL Browser discovery is needed. A fixed port often simplifies tightly scoped firewall rules, but the value must match the SQL network configuration. Port 1433 is common for a default instance, not a guarantee for every server.
Plan a certificate from a trusted authority with the names clients will actually use, and verify the SQL service can access its private key through the supported configuration. Current drivers can enforce encryption and certificate validation more strictly than old clients. Designing trust now avoids a later deployment that depends on disabling certificate validation.
Permit only the required source networks and services. Do not expose the database port publicly as a routine convenience. Application connectivity and administrative access may require different rules, and high-availability features require additional planned communication paths.
Resolve collation and installation settings in advance
Obtain the application's collation requirement, including case and accent sensitivity. Changing server collation later can be disruptive and is not the same as changing one application's configuration file. Choose the intended database engine directories, tempdb layout, service startup settings and administrator groups before Setup.
For automation, create a reviewed configuration file without embedding production passwords in shared storage or source control. Protect installation logs and configuration artifacts because they can reveal infrastructure details. Use the selected SQL release's own setup parameters rather than copying an old unattended command without checking it.
Establish a post-installation acceptance checklist
Run Setup's readiness checks and resolve failures before the installation window. After installation, inspect the engine version and servicing level, configure the agreed memory and storage settings, test a connection from an actual application host and verify certificate validation. An administrator connecting locally through shared memory does not test the network path the application will use.
Create a test database only under the agreed procedure, take a backup and perform a restore to an appropriate test destination. Verify scheduled backups and SQL Agent jobs under their real identities. Monitor disk growth, service events and failed logins. Keep a defined rollback path for a failed installation, including how to remove an unused instance without deleting unrelated shared components.
Use Microsoft's SQL and Windows compatibility matrix and the release-specific installation requirements as the starting references, then size and validate for the actual application.
Related procedures
How to Install .NET Framework Features on Windows Server; How to Configure a Group Managed Service Account for an Application; How to Create a System ODBC Data Source on Windows Server.
How to Install .NET Framework Features on Windows Server
Install the .NET component an application actually requires, rather than enabling every feature whose name contains “NET.” Windows includes…
How to Configure a Group Managed Service Account for an Application
A group Managed Service Account (gMSA) gives a compatible Windows application a domain identity whose password is managed by Active…
How to Create a System ODBC Data Source on Windows Server
A System ODBC data source gives a Windows application a named database connection configuration available at the machine level. It is often…
How to Configure a Dedicated Service Account for a Windows Application
A dedicated service account gives a Windows application an identity separate from the administrator who installed it. The goal is a stable,…
Making application environment settings reliable on Windows Server
Configure application environment values at the appropriate Windows scope, account for process inheritance and verify what the running…