For a Configuration Manager (formerly SCCM) CAS or primary site, install a supported 64-bit full SQL Server Database Engine instance before running Configuration Manager Setup. Use the required SQL_Latin1_General_CP1_CI_AS collation, Windows-based connectivity, current SQL client drivers, and a site-server computer account that can access SQL Server. SQL Server installation prepares the destination; it does not, by itself, migrate an existing SCCM hierarchy or database.
Microsoft’s support matrix changes with Configuration Manager releases. As of the documentation updated May 21, 2026, SQL Server 2025 RTM is supported with Configuration Manager 2603 and later, SQL Server 2022 is supported (with compatibility-level 160 support added in 2603), SQL Server 2019 requires CU5 or later, and SQL Server 2017 requires CU2 or later. SQL Server 2014 support ended in July 2024. Verify the exact pairing at Microsoft’s SQL Server support matrix before deployment.
Choose the migration scenario first
| Scenario | What you do with SQL Server |
|---|---|
| New destination hierarchy | Install supported SQL Server, then let Configuration Manager Setup create the new CAS or primary-site database. |
| Move an existing site database | Install SQL Server on the new computer, then follow the supported Configuration Manager database-move procedure. |
| Side-by-side hierarchy migration | Install SQL Server for the destination hierarchy, configure migration from the source hierarchy, and migrate supported objects such as collections, applications, packages, and boundaries. |
A side-by-side migration transfers supported data and configuration; it does not generally transfer site servers or other infrastructure computers. See what Configuration Manager migration transfers.
Select the right SQL Server installation
CAS and primary sites
- Use a 64-bit full SQL Server installation with Database Engine Services.
- Use either a default or named instance; a dedicated instance per site simplifies permissions, maintenance, resource control, and future moves.
- SQL Server can be local to the site server or on a dedicated remote server.
- SQL Server Express is not the normal supported database platform for a CAS or primary site.
Secondary sites
A secondary-site database must be on the secondary-site server. SQL Server Express or a full default or named SQL Server instance can be used in that scenario. Confirm the current rules in the support matrix.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Edition choice
SQL Server Standard is a common production choice for moderate deployments. Enterprise is appropriate when Enterprise-only capabilities or very large hierarchy scale require it; Microsoft notes that Standard on a CAS has a lower supported client scale than Enterprise. Developer is for non-production labs and testing under Microsoft licensing terms. Check current size-and-scale guidance before selecting an edition.
Prepare the server
Windows, identity, and naming
- Use a supported 64-bit Windows Server and a stable server name with reliable DNS.
- Use a domain-joined design where required by your organization.
- Prepare an account with sufficient SQL administrative rights for installation.
- Ensure the site server computer account can access SQL Server after setup. Microsoft’s site prerequisites are documented at Configuration Manager site-installation prerequisites.
- If SQL is installed with a domain user account, publish the required SPN correctly for Kerberos where applicable; see site administration security guidance.
Storage and memory
Plan storage for SQL data files, transaction logs, TempDB, and backups. Keep Configuration Manager content and site-server files from automatically competing with database volumes. Microsoft’s planning guidance recommends limiting SQL memory to about 50–80% of addressable memory when SQL shares the site server, or 80–90% on a dedicated SQL host. Minimum SQL buffer-pool reservations are 8 GB for a CAS, 8 GB for a primary site, and 4 GB for a secondary site. Treat these as planning ranges, not a substitute for workload sizing.
SQL client components
Install the SQL Native Client and ODBC components required by your Configuration Manager release. Microsoft states that ODBC Driver 18 or later is required from Configuration Manager 2303, and that version 18.4.1.1 or later is the minimum beginning with version 2503. Confirm the exact requirement in Microsoft’s servicing prerequisite guidance.
Rank #2
Install SQL Server
- Start current SQL Server media and choose New SQL Server stand-alone installation.
- Accept the license terms, install Setup Support Files and available updates, and continue.
- On Feature Selection, select Database Engine Services. Do not add Reporting Services or unrelated features merely because they are offered; reporting is a separate requirement.
- On Instance Configuration, choose the default instance or a named instance and record the exact name.
- Configure SQL service accounts according to your organization’s security standard.
- On Database Engine Configuration, select Windows authentication. SQL Server mixed mode can exist for other applications, but Configuration Manager database validation uses Windows identities.
- Add the administrators who must manage the instance during installation and operations.
- Open the Collation tab and select
SQL_Latin1_General_CP1_CI_AS. The instance and site database must use this collation, subject to Microsoft’s documented China GB18030 exception. Collation is difficult to change later, so do not accept an incompatible corporate default without checking support. - Complete setup and record the server and instance names, SQL service account, port, paths, edition, and build.
Apply the cumulative update or servicing level required by your Configuration Manager release. The documented minimums include SQL Server 2019 CU5 or later and SQL Server 2017 CU2 or later; SQL Server 2025 RTM support starts with Configuration Manager 2603. Recheck the current matrix after selecting a release.
Configure remote connectivity and permissions
- Verify forward and reverse DNS resolution between the site server and SQL Server.
- Enable the required SQL network protocol and prefer a controlled static port for a remote deployment.
- Open only the required firewall rules. TCP 1433 is an example, not a universal requirement; named instances can use another static port.
- Test using the exact server and instance notation, such as
SQLSERVER01orSQLSERVER01SCCM, only after the named instance and port discovery are configured. - Ensure the Setup account has the SQL rights required to create the site database and that the site server computer account retains the permissions required for normal operation. Do not remove rights immediately after installation without validating Microsoft’s supported operating model.
When SQL is installed on a domain account, SPN and Kerberos errors can look like ordinary login failures. Check DNS, firewall, SQL service status, protocol and port, Windows authentication, computer-account permissions, SPNs, and logs in that order.
Run the Configuration Manager prerequisite checker
From the Configuration Manager installation source, run:
Rank #3
prereqchk.exe /LOCALTo specify another installation path, use:
prereqchk.exe /LOCAL /InstallDir D:ConfigMgrThese switches are documented at Microsoft’s prerequisite-checker page. Resolve every blocking failure and investigate warnings involving SQL version, collation, drivers, permissions, or connectivity before continuing.
Install a new destination site
- Start Configuration Manager Setup and select the CAS or primary-site role.
- Enter the SQL Server fully qualified domain name.
- Enter the instance name when using a named instance.
- Specify the site database name and, where offered, database and log locations.
- Allow Setup to create the database, then monitor setup logs and component status.
For a new side-by-side migration, configure migration jobs only after the destination hierarchy is operational. Installing SQL Server does not copy source objects or establish the migration relationship.
Recommended Free Tools
Move an existing site database
- Take and verify a backup of the existing site database and the Configuration Manager site backup.
- Install a supported SQL Server version on the destination computer with the required collation, servicing level, drivers, connectivity, and permissions.
- Follow Microsoft’s supported Configuration Manager database-move process rather than attaching a database and changing settings informally.
- Point the site to the new instance and validate SMS Executive, site components, database connectivity, monitoring, reporting, and client operations.
Microsoft lists installing SQL on a new computer followed by a Configuration Manager database move as a supported SQL upgrade approach. In-place SQL upgrades and backup-and-recovery upgrades are also documented options at the SQL support page.
Rank #4
SQL settings Configuration Manager changes
| Setting | Required value |
|---|---|
clr enabled |
True |
nested triggers |
True |
max text repl size (B) |
2147483647 |
Configuration Manager configures these values during setup. Do not override them unless Microsoft Support directs you to do so.
Validate the completed installation
- SQL edition, version, cumulative update, and 64-bit architecture are supported for the Configuration Manager release.
- The instance and site database use
SQL_Latin1_General_CP1_CI_AS. - Database Engine is running and the site server can resolve and connect to it.
- Windows authentication succeeds and the site server computer account has the required access.
- The Configuration Manager database is online and logs show successful creation or move.
- SQL memory is capped appropriately for local or remote topology.
- The three Configuration Manager SQL settings have the required values.
- Backups are configured, restored in a test, and monitored.
- SQL patching, maintenance, antivirus exclusions, and monitoring are included in the operations plan.
- Reporting Services requirements are handled separately if reporting is being deployed.
Common failures and recovery
Wrong collation
Setup or prerequisite checks can reject an instance with the wrong collation. Reinstall SQL Server or create a correctly collated supported instance; changing only the database collation does not repair an incorrectly configured instance.
Unsupported SQL build
Install the required cumulative update or move to a supported release. “Newer” does not automatically mean supported for your Configuration Manager version.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated ODBC driver
Install the required ODBC Driver 18 build, then rerun prerequisite checks. Microsoft documents registry locations for verifying installed versions in its servicing troubleshooting guidance.
Remote SQL connection failure
Check DNS, firewall, SQL service, protocol, static port, instance name, Windows authentication, computer-account permissions, SPNs, and SQL/Configuration Manager logs.
Later operations fail after setup
Investigate lost computer-account permissions, an altered firewall or SQL configuration, an unplanned instance move, resource-heavy backup or maintenance jobs, unlimited SQL memory on a shared host, or restoration of the wrong database.
Topology and availability trade-offs
| Topology | Benefits | Costs |
|---|---|---|
| SQL on site server | Fewer network dependencies and simpler deployment. | SQL competes with site services for CPU, memory, storage, and maintenance windows. |
| Dedicated remote SQL | Resource isolation, centralized administration, and independent scaling. | Requires reliable network, firewall, permissions, DNS, and possibly SPN/Kerberos configuration. |
Always On availability groups and failover cluster instances are supported for appropriate designs, but they require separate planning for listeners, DNS, permissions, multi-subnet connectivity, backups, failover testing, and release compatibility. They are not prerequisites for an ordinary migration.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteLicensing and platform decisions
For production, compare Standard and Enterprise against client count, hierarchy scale, existing SQL licensing and Software Assurance, availability requirements, storage, and support contracts. Developer is intended for non-production use, while Express is generally limited to supported secondary-site or lab scenarios. Azure virtual machines running SQL Server add compute, storage, backup, and networking charges and must still meet Configuration Manager’s support matrix. Review Microsoft’s SQL licensing, Azure SQL virtual machine, and SQL Server Management Studio pages for current terms and tooling.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
