| title | description | author | ms.author | ms.reviewer | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Editions and supported features of SQL Server 2022 - Linux |
Editions and supported features of SQL Server 2022 on Linux |
rwestMSFT |
randolphwest |
amitkh, vanto |
10/20/2023 |
sql |
linux |
conceptual |
|
|
Editions and supported features of [!INCLUDEsssql22] on Linux
[!INCLUDE SQL Server - Linux]
This article provides details of features supported by the various editions of [!INCLUDEsssql22] on Linux. For more information on what's new in [!INCLUDEsssql22] on Windows, see What's new in SQL Server 2022.
Installation requirements vary based on your application needs. The different editions of [!INCLUDEssNoVersion] accommodate the unique performance, runtime, and price requirements of organizations and individuals. The [!INCLUDEssNoVersion] components that you install also depend on your specific requirements. The following sections help you understand how to make the best choice among the editions and components available in [!INCLUDEssNoVersion].
For the latest release notes and what's new information, see SQL Server 2022 on Linux release notes
For a list of SQL Server features not available on Linux, see Unsupported features and services.
[!INCLUDE sql-server-editions]
Use [!INCLUDEssNoVersion] with client/server applications
You can install just the [!INCLUDEssNoVersion] client components on a computer that is running client/server applications that connect directly to an instance of [!INCLUDEssNoVersion]. A client components installation is also a good option if you administer an instance of [!INCLUDEssNoVersion] on a database server, or if you plan to develop [!INCLUDEssNoVersion] applications.
[!INCLUDEssNoVersion] components
[!INCLUDEsssql22] on Linux supports the [!INCLUDEssDEnoversion]. The following table describes the features in the [!INCLUDEssDE].
| Server components | Description |
|---|---|
| [!INCLUDEssDEnoversion] | [!INCLUDEssDEnoversion] includes the [!INCLUDEssDE], the core service for storing, processing, and securing data, replication, Full-Text Search, tools for managing relational and XML data, and in database analytics integration. |
Developer, Enterprise Core, and Evaluation editions
For features supported by Developer, Enterprise Core, and Evaluation editions, see features listed for the SQL Server Enterprise edition in the following tables.
The Developer edition continues to support only one client for SQL Server Distributed Replay.
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Maximum compute capacity used by a single instance - [!INCLUDEssDEnoversion] 1 | Operating system maximum | Limited to lesser of 4 sockets or 24 cores | Limited to lesser of 4 sockets or 16 cores | Limited to lesser of 1 socket or 4 cores |
| Maximum compute capacity used by a single instance - [!INCLUDEssASnoversion] or [!INCLUDEssRSnoversion] | Operating system maximum | Limited to lesser of 4 sockets or 24 cores | Limited to lesser of 4 sockets or 16 cores | Limited to lesser of 1 socket or 4 cores |
| Maximum memory for buffer pool per instance of [!INCLUDEssDEnoversion] | Operating System Maximum | 128 GB | 64 GB | 1410 MB |
| Maximum capacity for buffer pool extension per instance of [!INCLUDEssDEnoversion] | 32 * (max server memory configuration) | 4 * (max server memory configuration) | N/A | N/A |
| Maximum memory for Columnstore segment cache per instance of [!INCLUDEssDEnoversion] | Unlimited memory | 32 GB | 16 GB | 352 MB |
| Maximum memory-optimized data size per database in [!INCLUDEssDEnoversion] | Unlimited memory | 32 GB | 16 GB | 352 MB |
| Maximum relational database size | 524 PB | 524 PB | 524 PB | 10 GB |
1 Enterprise edition with Server + Client Access License (CAL) based licensing (not available for new agreements) is limited to a maximum of 20 cores per SQL Server instance. There are no limits under the Core-based Server Licensing model. For more information, see Compute capacity limits by edition of SQL Server.
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Log shipping | Yes | Yes | Yes | No |
| Backup compression | Yes | Yes | No | No |
| Database snapshot | Yes | Yes | No | No |
| Always On failover cluster instance 1 | Yes | Yes | No | No |
| Always On availability groups 2 | Yes | No | No | No |
| Basic availability groups 3 | No | Yes | No | No |
| Minimum replica commit availability group | Yes | Yes | No | No |
| Clusterless availability group | Yes | Yes | No | No |
| Online page and file restore | Yes | No | No | No |
| Online indexing | Yes | No | No | No |
| Resumable online index rebuilds | Yes | No | No | No |
| Online schema change | Yes | No | No | No |
| Fast recovery | Yes | No | No | No |
| Mirrored backups | Yes | No | No | No |
| Hot add memory and CPU | Yes | No | No | No |
| Encrypted backup | Yes | Yes | No | No |
| Hybrid backup to Azure (backup to URL) | Yes | Yes | No | No |
1 On Enterprise edition, the number of nodes is the operating system maximum. On Standard edition, there is support for two nodes.
2 On Enterprise edition, provides support for up to 8 secondary replicas - including 2 synchronous secondary replicas.
3 Standard edition supports basic availability groups. A basic availability group supports two replicas, with one database. For more information about basic availability groups, see Basic Availability Groups.
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Columnstore 1 | Yes | Yes | Yes | Yes |
| Large object binaries in clustered columnstore indexes | Yes | Yes | Yes | Yes |
| Online nonclustered columnstore index rebuild | Yes | No | No | No |
| In-Memory OLTP 1 | Yes | Yes | Yes | Yes |
| Persistent Main Memory | Yes | Yes | Yes | Yes |
| Table and index partitioning | Yes | Yes | Yes | Yes |
| Data compression | Yes | Yes | Yes | Yes |
| Resource Governor | Yes | No | No | No |
| Partitioned Table Parallelism | Yes | No | No | No |
| NUMA Aware and Large Page Memory and Buffer Array Allocation | Yes | No | No | No |
| IO Resource Governance | Yes | No | No | No |
| Delayed Durability | Yes | Yes | Yes | Yes |
| Automatic tuning | Yes | No | No | No |
| Batch Mode Adaptive Joins | Yes | No | No | No |
| Batch Mode Memory Grant Feedback | Yes | No | No | No |
| Interleaved Execution for Multi-Statement Table Valued Functions | Yes | Yes | Yes | Yes |
| Bulk insert improvements | Yes | Yes | Yes | Yes |
1 In-Memory OLTP data size and columnstore segment cache are limited to the amount of memory specified by edition in the Scale Limits section. The max degree of parallelism is limited. The degree of process parallelism (DOP) for an index build is limited to 2 DOP for the Standard edition and 1 DOP for the Web and Express editions. This refers to columnstore indexes created over disk-based tables and memory-optimized tables.
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Row-level security | Yes | Yes | Yes | Yes |
| Always Encrypted | Yes | Yes | Yes | Yes |
| Dynamic data masking | Yes | Yes | Yes | Yes |
| Basic auditing | Yes | Yes | Yes | Yes |
| Fine grained auditing | Yes | Yes | Yes | Yes |
| Transparent database encryption (TDE) | Yes | Yes | No | No |
| User-defined roles | Yes | Yes | Yes | Yes |
| Contained databases | Yes | Yes | Yes | Yes |
| Encryption for backups | Yes | Yes | No | No |
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Dedicated admin connection | Yes | Yes | Yes | Yes 1 |
| PowerShell scripting support | Yes | Yes | Yes | Yes |
| Support for data-tier application component operations - extract, deploy, upgrade, delete | Yes | Yes | Yes | Yes |
| Policy automation (check on schedule and change) | Yes | Yes | Yes | No |
| Performance data collector | Yes | Yes | Yes | No |
| Standard performance reports | Yes | Yes | Yes | No |
| Plan guides and plan freezing for plan guides | Yes | Yes | Yes | No |
| Direct query of indexed views (using NOEXPAND hint) | Yes | Yes | Yes | Yes |
| Automatic indexed views maintenance | Yes | Yes | Yes | No |
| Distributed partitioned views | Yes | No | No | No |
| Parallel index operations | Yes | No | No | No |
| Automatic use of indexed view by query optimizer | Yes | No | No | No |
| Parallel consistency check | Yes | No | No | No |
| SQL Server Utility Control Point | Yes | No | No | No |
1 With trace flag.
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| JSON | Yes | Yes | Yes | Yes |
| Query Store | Yes | Yes | Yes | Yes |
| Temporal | Yes | Yes | Yes | Yes |
| Native XML support | Yes | Yes | Yes | Yes |
| XML indexing | Yes | Yes | Yes | Yes |
| MERGE & UPSERT capabilities | Yes | Yes | Yes | Yes |
| Date and time data types | Yes | Yes | Yes | Yes |
| Internationalization support | Yes | Yes | Yes | Yes |
| Full-text and semantic search | Yes | Yes | Yes | Yes |
| Specification of language in query | Yes | Yes | Yes | Yes |
| Service Broker (messaging) | Yes | Yes | No 1 | No 1 |
| Transact-SQL endpoints | Yes | Yes | Yes | No |
| Graph | Yes | Yes | Yes | Yes |
1 Client only.
For info about the Integration Services (SSIS) features supported by the editions of [!INCLUDEssNoVersion_md], see Integration Services features supported by the editions of SQL Server.
| Feature Name | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Spatial indexes | Yes | Yes | Yes | Yes |
| Planar and geodetic data types | Yes | Yes | Yes | Yes |
| Advanced spatial libraries | Yes | Yes | Yes | Yes |
| Import/export of industry-standard spatial data formats | Yes | Yes | Yes | Yes |
The following features and services aren't available for [!INCLUDEsssql22] on Linux. The support of these features will be increasingly enabled over time.
| Area | Unsupported feature or service |
|---|---|
| Data governance | Microsoft Purview integration |
| Database engine | Merge replication |
| Stretch DB | |
| Distributed query with third-party connections | |
| Linked servers to data sources other than [!INCLUDEssNoVersion] | |
System extended stored procedures (xp_cmdshell, etc.) |
|
| FileTable, FILESTREAM | |
| CLR assemblies with the EXTERNAL_ACCESS or UNSAFE permission set | |
| Buffer Pool Extension | |
| Backup to URL - page blob 1 | |
| SQL Server Agent | Subsystems: CmdExec, PowerShell, Queue Reader, SSIS, SSAS, SSRS |
| Alerts | |
| Managed Backup | |
| High Availability | Database mirroring |
| Security | Extensible Key Management (EKM) |
| Windows integrated authentication for linked servers | |
| Windows integrated authentication for availability group (AG) endpoints | |
| Always Encrypted with secure enclaves | |
| TLS 1.3 | |
| Services | SQL Server Browser |
| SQL Server R services 2 | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Data Quality Services | |
| Master Data Services |
1 Backup to URL is supported for block blobs, using the Shared Access Signature.
2 SQL Server R is supported within SQL Server, but SQL Server R services as a separate package isn't supported.
Note
The latest [!INCLUDE sssql22-md] features that depend on Azure Arc agent, including Microsoft Entra Authentication (previously known as Azure Active Directory authentication), Microsoft Purview, Pay-as-you-go (PAYG) for SQL Server, and Defender integration, are currently not supported for SQL Server deployed in containers. Azure Arc-enabled SQL Server doesn't support SQL Server running in containers.
[!INCLUDE editions-supported-features-windows]