- Editions and supported features of SQL Server 2019 on Linux
- Try SQL Server
- SQL Server editions
- Use SQL Server with client/server applications
- SQL Server components
- Scale limits
- RDBMS high availability
- RDBMS scalability and performance
- RDBMS security
- RDBMS manageability
- Programmability
- Integration Services
- Spatial and location services
- Unsupported features & services
- Next steps
- Выбор модели лицензирования для SQL Server на Linux
- Аннотация
- Дополнительные сведения
- Обратная связь
- Choose a licensing model for SQL Server on Linux
- Summary
- More information
Editions and supported features of SQL Server 2019 on Linux
This article provides details of features supported by the various editions of SQL Server 2019 on Linux. For editions and supported features of SQL Server on Windows, see SQL Server 2019 — Windows.
Installation requirements vary based on your application needs. The different editions of SQL Server accommodate the unique performance, runtime, and price requirements of organizations and individuals. The SQL Server 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 SQL Server.
For the latest release notes and what’s new information, see the following:
For a list of SQL Server features not available on Linux, see Unsupported features and services.
Try SQL Server
SQL Server editions
The following table describes the editions of SQL Server.
1 Unlimited virtualization is available on Enterprise edition for customers with Software Assurance. Deployments must comply with the licensing guide. For more information, see our pricing and licensing page.
Use SQL Server with client/server applications
You can install just the SQL Server client components on a computer that is running client/server applications that connect directly to an instance of SQL Server. A client components installation is also a good option if you administer an instance of SQL Server on a database server, or if you plan to develop SQL Server applications.
SQL Server components
SQL Server 2019 on Linux supports the SQL Server database engine. The following table describes the features in the database engine.
| Server components | Description |
|---|---|
| SQL Server Database Engine | SQL Server Database Engine includes the Database Engine, 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.
Scale limits
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Maximum compute capacity used by a single instance — SQL Server Database Engine 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 — Analysis Services or Reporting Services | 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 SQL Server Database Engine | Operating System Maximum | 128 GB | 64 GB | 1410 MB |
| Maximum capacity for buffer pool extension per instance of SQL Server Database Engine | 32 * (max server memory configuration) | 4 * (max server memory configuration) | N/A | N/A |
| Maximum memory for Columnstore segment cache per instance of SQL Server Database Engine | Unlimited memory | 32 GB | 16 GB | 352 MB |
| Maximum memory-optimized data size per database in SQL Server Database Engine | 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.
RDBMS high availability
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Log shipping | ||||
| Backup compression | ||||
| Database snapshot | ||||
| Always On failover cluster instance 1 | ||||
| Always On availability groups 2 | ||||
| Basic availability groups 3 | ||||
| Minimum replica commit availability group | ||||
| Clusterless availability group | ||||
| Online page and file restore | ||||
| Online indexing | ||||
| Resumable online index rebuilds | ||||
| Online schema change | ||||
| Fast recovery | ||||
| Mirrored backups | ||||
| Hot add memory and CPU | ||||
| Encrypted backup | ||||
| Hybrid backup to Azure (backup to URL) |
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.
RDBMS scalability and performance
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Columnstore 1 | ||||
| Large object binaries in clustered columnstore indexes | ||||
| Online nonclustered columnstore index rebuild | ||||
| In-Memory OLTP 1 | ||||
| Persistent Main Memory | ||||
| Table and index partitioning | ||||
| Data compression | ||||
| Resource Governor | ||||
| Partitioned Table Parallelism | ||||
| NUMA Aware and Large Page Memory and Buffer Array Allocation | ||||
| IO Resource Governance | ||||
| Delayed Durability | ||||
| Automatic tuning | ||||
| Batch Mode Adaptive Joins | ||||
| Batch Mode Memory Grant Feedback | ||||
| Interleaved Execution for Multi-Statement Table Valued Functions | ||||
| Bulk insert improvements |
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.
RDBMS security
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Row-level security | ||||
| Always Encrypted | ||||
| Dynamic data masking | ||||
| Basic auditing | ||||
| Fine grained auditing | ||||
| Transparent database encryption (TDE) | ||||
| User-defined roles | ||||
| Contained databases | ||||
| Encryption for backups |
RDBMS manageability
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Dedicated admin connection | Yes 1 | |||
| PowerShell scripting support | ||||
| Support for data-tier application component operations — extract, deploy, upgrade, delete | ||||
| Policy automation (check on schedule and change) | ||||
| Performance data collector | ||||
| Standard performance reports | ||||
| Plan guides and plan freezing for plan guides | ||||
| Direct query of indexed views (using NOEXPAND hint) | ||||
| Automatic indexed views maintenance | ||||
| Distributed partitioned views | ||||
| Parallel indexed operations | ||||
| Automatic use of indexed view by query optimizer | ||||
| Parallel consistency check | ||||
| SQL Server Utility Control Point |
Programmability
| Feature | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| JSON | ||||
| Query Store | ||||
| Temporal | ||||
| Native XML support | ||||
| XML indexing | ||||
| MERGE & UPSERT capabilities | ||||
| Date and Time datatypes | ||||
| Internationalization support | ||||
| Full-text and semantic search | ||||
| Specification of language in query | ||||
| Service Broker (messaging) | No 1 | No 1 | ||
| Transact-SQL endpoints | ||||
| Graph |
Integration Services
For info about the Integration Services (SSIS) features supported by the editions of SQL Server, see Integration Services features supported by the editions of SQL Server.
Spatial and location services
| Feature Name | Enterprise | Standard | Web | Express |
|---|---|---|---|---|
| Spatial indexes | ||||
| Planar and geodetic datatypes | ||||
| Advanced spatial libraries | ||||
| Import/export of industry-standard spatial data formats |
Unsupported features & services
The following features and services aren’t available for SQL Server 2019 on Linux. The support of these features will be increasingly enabled over time.
| Area | Unsupported feature or service |
|---|---|
| Database engine | Merge replication |
| Stretch DB | |
| Distributed query with 3rd-party connections | |
| Linked Servers to data sources other than SQL Server | |
| 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 2 | |
| SQL Server Agent | Subsystems: CmdExec, PowerShell, Queue Reader, SSIS, SSAS, SSRS |
| Alerts | |
| Managed Backup | |
| High Availability | Database mirroring |
| Security | Extensible Key Management (EKM) |
| Active Directory Authentication for Linked Servers | |
| Active Directory Authentication for Availability Group (AG) Endpoints | |
| Services | SQL Server Browser |
| SQL Server R services 1 | |
| StreamInsight | |
| Analysis Services | |
| Reporting Services | |
| Data Quality Services | |
| Master Data Services |
1 SQL Server R is supported within SQL Server, but SQL Server R services as a separate package isn’t supported.
2 Backup to URL is supported for block blobs, using the Shared Access Signature.
Next steps
Выбор модели лицензирования для SQL Server на Linux
В этой статье описывается, как выбрать модель лицензирования для SQL Server на Linux.
Исходная версия продукта: SQL Server 2017 в Linux (все выпуски)
Исходный номер базы знаний: 4475751
Аннотация
Если вы устанавливаете Microsoft SQL Server на Linux с помощью средства установки mssql-conf и приобрели соответствующую лицензию через Центр обслуживания корпоративного лицензирования (VLSC), вы можете выбрать один из соответствующих параметров PAID из следующих SQL Server выпусков:
- Оценка (бесплатно, без прав на использование в рабочей среду, ограничение в 180 дней)
- Разработчик (бесплатно, без прав на использование в рабочей среду)
- Express (бесплатно)
- Web (PAID)
- Standard (PAID)
- Корпоративная (ПЛАТНАЯ)
- Enterprise Core (PAID)
- «Я приобрел лицензию через канал розничной торговли и у меня есть ключ продукта для ввода».
Дополнительные сведения
Дополнительные сведения см. в следующих разделах SQL Server на Linux часто задаваемых вопросов.
Как работает лицензирование в Linux?
SQL Server лицензии для Windows и Linux. Вы выбираете платформу по вашему выбору в процессе лицензирования. Дополнительные сведения см. в разделе о лицензировании SQL Server.
Какой выпуск SQL Server выбрать, если я уже приобрел его?
При запуске программы установки mssql-conf предоставляются следующие параметры установки:
Выберите выпуск SQL Server:
- Оценка (бесплатно, без прав на использование в рабочей среду, ограничение в 180 дней)
- Разработчик (бесплатно, без прав на использование в рабочей среду)
- Express (бесплатно)
- Web (PAID)
- Standard (PAID)
- Корпоративная (ПЛАТНАЯ)
- Enterprise Core (PAID)
- Я приобрел лицензию через канал розничной торговли и у меня есть ключ продукта для ввода.
Если вы получили лицензию в рамках корпоративного лицензирования Соглашение Enterprise подписки MSDN, необходимо выбрать один из вариантов с 4 по 7. Если вы приобрели выпуск Standard через розничный канал, необходимо выбрать вариант 8.
Обратная связь
Были ли сведения на этой странице полезными?
Choose a licensing model for SQL Server on Linux
This article describes how to choose a licensing model for SQL Server on Linux.
Original product version: SQL Server 2017 on Linux (all editions)
Original KB number: 4475751
Summary
If you install Microsoft SQL Server on Linux by using the mssql-conf Setup tool, and if you purchased the appropriate license through the Volume Licensing Service Center (VLSC), you can select one of the appropriate PAID options from among the following SQL Server editions:
- Evaluation (free, no production use rights, 180-day limit)
- Developer (free, no production use rights)
- Express (free)
- Web (PAID)
- Standard (PAID)
- Enterprise (PAID)
- Enterprise Core (PAID)
- «I bought a license through a retail sales channel and have a product key to enter.»
More information
For more information, see the following sections from SQL Server on Linux Frequently Asked Questions (FAQ).
How does licensing work on Linux?
SQL Server is licensed the same way for both Windows and Linux. You select the platform of your choice during the licensing process. For more information, see How to license SQL Server.
Which edition of SQL Server should I choose if I have already purchased it?
When you run mssql-conf Setup, you are provided the following installation options:
Choose an edition of SQL Server:
- Evaluation (free, no production use rights, 180-day limit)
- Developer (free, no production use rights)
- Express (free)
- Web (PAID)
- Standard (PAID)
- Enterprise (PAID)
- Enterprise Core (PAID)
- I bought a license through a retail sales channel and have a product key to enter.
If you obtained your license through Volume Licensing as part of an Enterprise Agreement or through your MSDN subscription, you must select from among options 4 through 7. If you purchased a Standard edition through a retail channel, you must select option 8.