Microsoft Configuration Manager
GeneralSupported SQL Server versions
In brief
Updated Microsoft Intune documentation in intune/configmgr/core/plan-design/configs/support-for-sql-server-versions.md.
What Intune admins need to know
Review the underlying documentation change to determine whether it affects tenant configuration or rollout plans.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
Open full page diff →The comparison below shows only the changed extract. Open the full-page diff for complete context.
title: Supported SQL Server versions
description: GetLearn which SQL Server versionversions, editions, and configuration requirements for hosting acompatibility levels Configuration Manager site database.supports.
ms.date: 05/21/07/28/2026
ms.subservice: core-infrastructure
ms.topic: reference
ms.collection: tier3
Applies to: Configuration Manager (current branch)
Each Configuration Manager site requires a supported SQL Server version and configuration to host the site database. For required and optional settings, see Supported configurations for SQL Server.
SQL Server instances and locations
Central administration site and primary sites
Only the Database Engine Services feature is required for each site server.
Configuration Manager database replication doesn't require the SQL Server replication feature. However, this SQL Server configuration is required when you use database replicas for management points.
Use a dedicated instance of SQL Server for each site. The instance can be a named instance or the default instance.
The site database must use a full installation of SQL Server.
The data warehouse uses a separate database. You can host it on the site database server, or a separate SQL Server. For more information, see The data warehouse service point for Configuration Manager. The following configurations aren't supported:
| SQL Version | Minimum Required Update | Supported Site Types | Notes | Starting in version 2409, support for SQL Server Configuration Manager requires that the compatibility level for the site database is no less than the lowest supported SQL Server version for your Configuration Manager version.
For more information on SQL Server compatibility levels and how to set them, see ALTER DATABASE Compatibility Level (Transact-SQL).
SQL Server Reporting Services is required for installing a reporting services point that lets you run reports. Configuration Manager supports the same versions of SQL Server for reporting as it does for the site database.
After you upgrade SQL Server from a previous version, you might see the following error: Report Builder Does Not Exist.
To resolve this error, you must reinstall the reporting services point site system role.
If you have a firewall enabled on the computer that is running SQL Server, make sure that it's configured to allow the ports that are being used by your deployment and at any locations on the network between computers that communicate with the SQL Server.
For an example of how to configure SQL Server to use a specific port, see Configure a server to listen on a specific TCP port. If you need to upgrade your version of SQL Server, use one of the following methods, from easy to more complex:The site database must use a full installation of SQL Server.
Limitations to supportThe following configurations aren't supported:
Standard / Enterprise SQL Editions| SQL Version | Minimum Required Update | Supported Site Types | Notes |Starting in version 2409, support for SQL Server 2014 is deprecated. Required configurations for SQL ServerThe following configurations are required by all installations of SQL Server that you use for a site database, including SQL Server Express. When Configuration Manager installs SQL Server Express as part of a secondary site installation, it automatically creates these configurations.SQL Server architecture versionConfiguration Manager requires a 64-bit version of SQL Server to host the site database.SQL Instance and Database collationsAt each site, both the instance of SQL Server that's used for the site and the site database must use the following collation: SQL_Latin1_General_CP1_CI_AS.Configuration Manager supports two exceptions to this collation for the China GB18030 standard. For more information, see International support.
SQL Server features
Windows authenticationConfiguration Manager requires Windows authentication to validate connections to the database.SQL Server instance
Central administration site and primary sites
Data warehouse service point
Limitations to support
SQL Server
memoryarchitectureReserve memoryConfiguration Manager requires a 64-bit version of SQL Server to host the site database.Standard / Enterprise SQL Editions
by using SQL Server Management Studio. Set the Minimum server memory setting under Server Memory Options. For more information about how to configure this setting, see SQL Server memory server configuration options.2014 is deprecated.
For a database server that you install on the same computer as the site server: Limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory.For a dedicated database server that's remote from the site server: Limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory.For a memory reserve for the buffer pool of each SQL Server instance in use:For a central administration site: Set a minimum of 8 GB.For a primary site: Set a minimum of 8 GB.For a secondary site: Set a minimum of 4 GB.Other required SQL Server configurationsConfiguration Manager sets the below SQL Server configurations during setup to function correctly. They apply for both standalone primary site and hierarchy scenarios. Do not alter them unless instructed by Microsoft support.Display nameCanonical nameRequired valueMore information linkCLR integrationclr enabledTrueIntroduction to SQL Server CLR Integration.Allow Triggers to Fire Othersnested triggersTrueConfigure the nested triggers server configuration option.Max Text Replication Sizemax text repl size (B)2147483647Configure the max text repl size server configuration option.Required SQL database configurationsDatabase compatibility level
SQL Server version
Supported compatibility levels
Recommended level
SQL Server 2025 (since version 2603)
170, 160, 150, 140, 130, 120, 110
170
SQL Server 2022
160 (since version 2603), 150, 140, 130, 120, 110
150
SQL Server 2019
150, 140, 130, 120, 110
150
SQL Server 2017
140, 130, 120, 110
140
Other required database configurationsConfiguration Manager sets the below database configurations during setup to function correctly. They apply for both standalone primary site and hierarchy scenarios - as well as for SQL Always On configurations.Do not alter them unless instructed by Microsoft support. The Support policies for manual database changes article applies for database options.Display nameCanonical nameRequired valueMore information linkDatabase ownerowner_sidsaALTER AUTHORIZATION for databasesChange trackingCHANGE_TRACKINGTrue (ON)Enable change trackingRecursive Triggers EnabledRECURSIVE_TRIGGERSTrue (ON)Recursive TriggersBroker EnabledENABLE_BROKERTrue (ON)Activate Service Broker in a databaseHonor Broker PriorityHONOR_BROKER_PRIORITYTrue (ON)Enable conversation prioritiesTrustworthyTRUSTWORTHYTrue (ON)TRUSTWORTHY database propertyAllow Snapshot IsolationALLOW_SNAPSHOT_ISOLATIONTrue (ON)Snapshot Isolation in SQL ServerIs Read Committed Snapshot OnREAD_COMMITTED_SNAPSHOTTrue (ON)Set Transaction Isolation LevelANSI Nulls EnabledANSI_NULLSTrue (ON)SET ANSI_NULLSANSI Padding EnabledANSI_PADDINGTrue (ON)SET ANSI_PADDINGANSI Warnings EnabledANSI_WARNINGSTrue (ON)SET ANSI_WARNINGSArithmetic Abort EnabledARITHABORTTrue (ON)SET ARITHABORTConcatenate Null Yields NullCONCAT_NULL_YIELDS_NULLTrue (ON)SET CONCAT_NULL_YIELDS_NULLQuoted Identifiers EnabledQUOTED_IDENTIFIERTrue (ON)SET QUOTED_IDENTIFIERNumeric Round-abortNUMERIC_ROUNDABORTFalse (OFF)SET NUMERIC_ROUNDABORT Optional configurations for SQL ServerThe following configurations are optional for each database that uses a full SQL Server installation.SQL Server serviceYou can configure the SQL Server service to run using:A low rights domain user account:This configuration is a best practice and might require you to manually register the service principal name (SPN) for the account.The local system account of the computer that runs SQL Server:Use the local system account to simplify the configuration process.When you use the local system account, Configuration Manager automatically registers the SPN for the SQL Server service.Using the local system account for the SQL Server service isn't a SQL Server best practice.When the computer running SQL Server doesn't use its local system account to run the SQL Server service, configure the SPN of the account that runs the SQL Server service in Active Directory Domain Services. (When the system account is used, the SPN is automatically registered for you.)For information about SPNs for the site database, see Manage the SPN for the site database server.For information about how to change the account that is used by the SQL Server service, see SCM Services - Change the service startup account.SQL Extended Protection for AuthenticationStarting from version 2409, Configuration Manager supports SQL extended protection for authentication. It's a security feature that enhances protection against MITM attacks, making SQL server more secure when connections are made using extended protection. These enhancements collectively reduce the risk of unauthorized access and protect sensitive data managed by the SQL Server database engine.For more information, see Connect to the Database Engine Using Extended Protection.SQL Server Reporting Services
Data warehouse service pointThe data warehouse uses a separate database. You can host it on the site database server, or a separate SQL Server. For more information, see The data warehouse service point for Configuration Manager.SQL Server portsFor communication to the SQL Server database engine and for intersite replication, you can use the default SQL Server port configurations or specify custom ports:Intersite communications use the SQL Server Service Broker, which uses port TCP 4022 by default.Intrasite communications between the SQL Server database engine and various Configuration Manager site system roles use port TCP 1433 by default. The following site system roles communicate directly with the SQL Server database:Management pointSMS Provider computerReporting services pointSite serverWhen a computer running SQL Server hosts a database from more than one site, each database must use a separate instance of SQL Server. Also, each instance must be configured to use a unique set of ports.
Upgrade options for SQL Server
@@ -1,7 +1,7 @@ --- title: Supported SQL Server versions-description: Get SQL Server version and configuration requirements for hosting a Configuration Manager site database.-ms.date: 05/21/2026+description: Learn which SQL Server versions, editions, and compatibility levels Configuration Manager supports.+ms.date: 07/28/2026 ms.subservice: core-infrastructure ms.topic: reference ms.collection: tier3@@ -12,10 +12,20 @@ ms.service: microsoft-endpoint-configuration-manager *Applies to: Configuration Manager (current branch)* -Each Configuration Manager site requires a supported SQL Server version and configuration to host the site database.+Each Configuration Manager site requires a supported SQL Server version to host the site database. For required and optional settings, see [Supported configurations for SQL Server](supported-configurations-for-sql-server.md). ## <a name="bkmk_Instances"></a> SQL Server instances and locations +### SQL Server features++Only the **Database Engine Services** feature is required for each site server.++Configuration Manager database replication doesn't require the **SQL Server replication** feature. However, this SQL Server configuration is required when you use [database replicas for management points](../../servers/deploy/configure/database-replicas-for-management-points.md).++### SQL Server instance++Use a dedicated instance of SQL Server for each site. The instance can be a **named instance** or the **default instance**.+ ### Central administration site and primary sites The site database must use a full installation of SQL Server.@@ -44,6 +54,10 @@ SQL Server must be located on the site server computer. > [!IMPORTANT] > Upgrade SQL 2012 or 2014 Express, Standard, Enterprise edition to SQl 2016 or latest version. Visual C++ Redistributable need to be upgraded to latest version on Secondary site: [Download Latest Microsoft Visual C++ Redistributable Version](https://aka.ms/vs/17/release/vc_redist.x64.exe). +### Data warehouse service point++The data warehouse uses a separate database. You can host it on the site database server, or a separate SQL Server. For more information, see [The data warehouse service point for Configuration Manager](../../servers/manage/data-warehouse.md).+ ### Limitations to support The following configurations aren't supported:@@ -71,6 +85,10 @@ Unless specified otherwise, the following versions of SQL Server are supported w > [!IMPORTANT] > When you use SQL Server Standard for the database at the central administration site, you limit the total number of clients that a hierarchy can support. See [Size and scale numbers](size-and-scale-numbers.md). +### SQL Server architecture++Configuration Manager requires a 64-bit version of SQL Server to host the site database.+ ### Standard / Enterprise SQL Editions | SQL Version | Minimum Required Update | Supported Site Types | Notes |@@ -128,61 +146,7 @@ You can use this version with the minimum service pack and cumulative update sup > Starting in version 2409, support for SQL Server 2014 is deprecated.<!--10092858--> > <!--Its support lifecycle ends in July 2024. Plan to upgrade all database servers before that time. For more information, see [SQL Server](../changes/deprecated/removed-and-deprecated-server.md#sql-server).--> -## <a name="bkmk_SQLConfig"></a> Required configurations for SQL Server--The following configurations are required by all installations of SQL Server that you use for a site database, including SQL Server Express. When Configuration Manager installs SQL Server Express as part of a secondary site installation, it automatically creates these configurations.--### SQL Server architecture version--Configuration Manager requires a 64-bit version of SQL Server to host the site database.--### SQL Instance and Database collations--At each site, both the instance of SQL Server that's used for the site and the site database must use the following collation: **SQL_Latin1_General_CP1_CI_AS**.--Configuration Manager supports two exceptions to this collation for the China GB18030 standard. For more information, see [International support](../hierarchy/international-support.md).--### SQL Server features--Only the **Database Engine Services** feature is required for each site server.--Configuration Manager database replication doesn't require the **SQL Server replication** feature. However, this SQL Server configuration is required when you use [database replicas for management points](../../servers/deploy/configure/database-replicas-for-management-points.md).--### Windows authentication--Configuration Manager requires **Windows authentication** to validate connections to the database.--### SQL Server instance--Use a dedicated instance of SQL Server for each site. The instance can be a **named instance** or the **default instance**.--### SQL Server memory--Reserve memory for SQL Server by using SQL Server Management Studio. Set the **Minimum server memory** setting under **Server Memory Options**. For more information about how to configure this setting, see [SQL Server memory server configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options).--- **For a database server that you install on the same computer as the site server**: Limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory.--- **For a dedicated database server that's remote from the site server**: Limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory.--- **For a memory reserve for the buffer pool of each SQL Server instance in use**:-- - For a central administration site: Set a minimum of 8 GB.- - For a primary site: Set a minimum of 8 GB.- - For a secondary site: Set a minimum of 4 GB.--### Other required SQL Server configurations--Configuration Manager sets the below SQL Server configurations during setup to function correctly. They apply for both standalone primary site and hierarchy scenarios. Do not alter them unless instructed by Microsoft support.--| Display name | Canonical name | Required value | More information link |-|--------------|---------------|----------------|------------------|-| CLR integration | `clr enabled` | True | [Introduction to SQL Server CLR Integration](/dotnet/framework/data/adonet/sql/introduction-to-sql-server-clr-integration). |-| Allow Triggers to Fire Others | `nested triggers` | True | [Configure the nested triggers server configuration option](/sql/database-engine/configure-windows/configure-the-nested-triggers-server-configuration-option). |-| Max Text Replication Size | `max text repl size (B)` | 2147483647 | [Configure the max text repl size server configuration option](/sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option). |--## <a name="bkmk_DBConfig"></a>Required SQL database configurations--### Database compatibility level+## Database compatibility level Configuration Manager requires that the compatibility level for the site database is no less than the lowest supported SQL Server version for your Configuration Manager version. @@ -192,7 +156,7 @@ The following table identifies the recommended compatibility levels for Configur |SQL Server version | Supported compatibility levels | Recommended level | |----------------|--------------------|--------|-| SQL Server 2025 | 170, 160, 150, 140, 130, 120, 110 | 170 |+| SQL Server 2025 (since version 2603) | 170, 160, 150, 140, 130, 120, 110 | 170 | | SQL Server 2022 | 160 (since version 2603), 150, 140, 130, 120, 110 | 150 | | SQL Server 2019 | 150, 140, 130, 120, 110 | 150 | | SQL Server 2017 | 140, 130, 120, 110 | 140 |@@ -207,62 +171,7 @@ SELECT name, compatibility_level FROM sys.databases For more information on SQL Server compatibility levels and how to set them, see [ALTER DATABASE Compatibility Level (Transact-SQL)](/sql/t-sql/statements/alter-database-transact-sql-compatibility-level). -### Other required database configurations--Configuration Manager sets the below database configurations during setup to function correctly. They apply for both standalone primary site and hierarchy scenarios - as well as for SQL Always On configurations.--Do not alter them unless instructed by Microsoft support. The [Support policies for manual database changes](/troubleshoot/mem/configmgr/setup-migrate-backup-recovery/support-policy-for-manual-database-changes) article applies for database options.--| Display name | Canonical name | Required value | More information link |-|--------------|---------------|----------------|------------------|-| Database owner | `owner_sid` | `sa` | [ALTER AUTHORIZATION for databases](/sql/t-sql/statements/alter-authorization-transact-sql#alter-authorization-for-databases) |-| Change tracking | `CHANGE_TRACKING` | True (ON) | [Enable change tracking](/sql/relational-databases/track-changes/about-change-tracking-sql-server) |-| Recursive Triggers Enabled | `RECURSIVE_TRIGGERS` | True (ON) | [Recursive Triggers](/sql/relational-databases/triggers/create-nested-triggers#recursive-triggers) |-| Broker Enabled | `ENABLE_BROKER` | True (ON) | [Activate Service Broker in a database](/sql/database-engine/service-broker/how-to-activate-service-broker-message-delivery-in-databases-transact-sql#activate-service-broker-in-a-database) |-| Honor Broker Priority | `HONOR_BROKER_PRIORITY` | True (ON) | [Enable conversation priorities](/sql/database-engine/service-broker/managing-conversation-priorities#enable-conversation-priorities) |-| Trustworthy | `TRUSTWORTHY` | True (ON) | [TRUSTWORTHY database property](/sql/relational-databases/security/trustworthy-database-property) |-| Allow Snapshot Isolation | `ALLOW_SNAPSHOT_ISOLATION` | True (ON) | [Snapshot Isolation in SQL Server](/dotnet/framework/data/adonet/sql/snapshot-isolation-in-sql-server) |-| Is Read Committed Snapshot On | `READ_COMMITTED_SNAPSHOT` | True (ON) | [Set Transaction Isolation Level](/sql/t-sql/statements/set-transaction-isolation-level-transact-sql) |-| ANSI Nulls Enabled | `ANSI_NULLS` | True (ON) | [SET ANSI_NULLS](/sql/t-sql/statements/set-ansi-nulls-transact-sql) |-| ANSI Padding Enabled | `ANSI_PADDING` | True (ON) | [SET ANSI_PADDING](/sql/t-sql/statements/set-ansi-padding-transact-sql) |-| ANSI Warnings Enabled | `ANSI_WARNINGS` | True (ON) | [SET ANSI_WARNINGS](/sql/t-sql/statements/set-ansi-warnings-transact-sql) |-| Arithmetic Abort Enabled | `ARITHABORT` | True (ON) | [SET ARITHABORT](/sql/t-sql/statements/set-arithabort-transact-sql) |-| Concatenate Null Yields Null | `CONCAT_NULL_YIELDS_NULL` | True (ON) | [SET CONCAT_NULL_YIELDS_NULL](/sql/t-sql/statements/set-concat-null-yields-null-transact-sql) |-| Quoted Identifiers Enabled | `QUOTED_IDENTIFIER` | True (ON) | [SET QUOTED_IDENTIFIER](/sql/t-sql/statements/set-quoted-identifier-transact-sql) |-| Numeric Round-abort | `NUMERIC_ROUNDABORT` | False (OFF) | [SET NUMERIC_ROUNDABORT](/sql/t-sql/statements/set-numeric-roundabort-transact-sql) |--## <a name="bkmk_optional"></a> Optional configurations for SQL Server--The following configurations are optional for each database that uses a full SQL Server installation.--### SQL Server service--You can configure the SQL Server service to run using:--- A *low rights domain user* account:-- - This configuration is a best practice and might require you to manually register the service principal name (SPN) for the account.--- The **local system** account of the computer that runs SQL Server:-- - Use the local system account to simplify the configuration process.- - When you use the local system account, Configuration Manager automatically registers the SPN for the SQL Server service.- - Using the local system account for the SQL Server service isn't a SQL Server best practice.--When the computer running SQL Server doesn't use its local system account to run the SQL Server service, configure the SPN of the account that runs the SQL Server service in Active Directory Domain Services. (When the system account is used, the SPN is automatically registered for you.)--For information about SPNs for the site database, see [Manage the SPN for the site database server](../../servers/manage/modify-your-infrastructure.md#bkmk_SPN).--For information about how to change the account that is used by the SQL Server service, see [SCM Services - Change the service startup account](/sql/database-engine/configure-windows/scm-services-change-the-service-startup-account).--### SQL Extended Protection for Authentication-<!--24501008-->--Starting from version 2409, Configuration Manager supports SQL extended protection for authentication. It's a security feature that enhances protection against MITM attacks, making SQL server more secure when connections are made using extended protection. These enhancements collectively reduce the risk of unauthorized access and protect sensitive data managed by the SQL Server database engine.--For more information, see [Connect to the Database Engine Using Extended Protection](/sql/database-engine/configure-windows/connect-to-the-database-engine-using-extended-protection).--### SQL Server Reporting Services+## SQL Server Reporting Services SQL Server Reporting Services is required for installing a reporting services point that lets you run reports. Configuration Manager supports the same versions of SQL Server for reporting as it does for the site database. @@ -272,31 +181,6 @@ For more information, see [Prerequisites for reporting in Configuration Manager] > After you upgrade SQL Server from a previous version, you might see the following error: *Report Builder Does Not Exist*. > To resolve this error, you must reinstall the reporting services point site system role. -### Data warehouse service point--The data warehouse uses a separate database. You can host it on the site database server, or a separate SQL Server. For more information, see [The data warehouse service point for Configuration Manager](../../servers/manage/data-warehouse.md).--### SQL Server ports--For communication to the SQL Server database engine and for intersite replication, you can use the default SQL Server port configurations or specify custom ports:--- **Intersite communications** use the SQL Server Service Broker, which uses port TCP 4022 by default.-- **Intrasite communications** between the SQL Server database engine and various Configuration Manager site system roles use port TCP 1433 by default. The following site system roles communicate directly with the SQL Server database:-- - Management point- - SMS Provider computer- - Reporting services point- - Site server--When a computer running SQL Server hosts a database from more than one site, each database must use a separate instance of SQL Server. Also, each instance must be configured to use a unique set of ports.--> [!WARNING]-> Configuration Manager doesn't support dynamic ports. Because SQL Server named instances by default use dynamic ports for connections to the database engine, when you use a named instance, you must manually configure the static port that you want to use for intrasite communication.--If you have a firewall enabled on the computer that is running SQL Server, make sure that it's configured to allow the ports that are being used by your deployment and at any locations on the network between computers that communicate with the SQL Server.--For an example of how to configure SQL Server to use a specific port, see [Configure a server to listen on a specific TCP port](/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port).- ## Upgrade options for SQL Server If you need to upgrade your version of SQL Server, use one of the following methods, from easy to more complex: