What is included in Microsoft SQL Server 2017 Standard?

Database Engine – Relational engine for storing and querying production data.
Basic Availability Groups – Two-replica failover protecting a single database.
Reporting Services – Builds paginated reports and dashboards from live data.
Integration Services – Moves and transforms data between systems and warehouses.
Core Capacity – Uses up to 24 cores and 128 GB RAM.
Important – Transparent Data Encryption is not included in this 2017 edition.

What are the main benefits of Microsoft SQL Server 2017 Standard?

SQL Server 2017 Standard is the mid-tier relational database for departmental and small-to-medium business workloads. It runs on Windows, Linux, and Docker, and covers transactional databases, reporting, and ETL without the cost of Enterprise.

Cross-Platform – Same engine on Windows, Linux, and containers.
Built-In BI – Reporting and Integration Services ship at no extra cost.
Basic High Availability – Two-node clustering and single-database availability groups.
Licensing Choice – Per-core or Server plus CAL model available.
Predictable Limits – 24 cores and 128 GB cover most line-of-business apps.
In-Place Upgrade – Upgrades existing 2012 to 2016 instances directly.

SQL Server 2017–2025 Buying Guide: License Models and CALs
How to read the per-core and Server-plus-CAL models and pick the right SQL product without overpaying.

What does SQL Server 2017 Standard do?

It stores, secures, and queries relational data for business applications such as ERP back ends, accounting systems, and departmental web apps. The Standard edition includes the full Database Engine plus Reporting Services and Integration Services, so a single license covers transactional storage, scheduled ETL jobs, and report generation. SQL Server 2017 was also the first release to run natively on Linux and in Docker containers, which lets teams standardise on one engine across mixed infrastructure. For typical line-of-business databases under 128 GB of active memory, Standard delivers the same query engine as Enterprise without the higher per-core cost.

Who is SQL Server 2017 Standard best suited for?

It fits small and medium businesses running departmental databases, accounting or ERP back ends, and internal web applications that stay within 24 cores and 128 GB of engine memory. Because Reporting Services and Integration Services are included, a finance team can schedule nightly data loads and publish paginated reports from one licensed instance instead of buying separate tools. Organisations that need unlimited memory, online index rebuilds, or Always On availability groups with multiple readable secondaries will hit Standard's ceilings and should evaluate Enterprise instead. For most non-mission-critical workloads, Standard's limits are higher than the actual hardware in use.

How does SQL Server 2017 Standard compare to the Enterprise edition?

The query engine is identical, but Standard caps compute at the lesser of 4 sockets or 24 cores and buffer pool memory at 128 GB per instance, while Enterprise scales to the operating system maximum. Standard supports basic availability groups (two replicas, one database) and two-node failover clustering, whereas Enterprise adds Always On availability groups with up to eight secondaries, online index rebuilds, partitioned table parallelism, and Resource Governor. Columnstore batch-mode queries are limited to two cores of parallelism on Standard, which slows large analytical scans compared with Enterprise. For transactional apps and modest reporting this gap rarely matters; for large data warehouses or 24/7 mission-critical systems it does.

SQL Server 2022, 2019, and 2017: Features and Differences
Side-by-side look at what each version adds, including the features that moved into Standard over time.

Does SQL Server 2017 Standard support Transparent Data Encryption?

No. In SQL Server 2017, Transparent Data Encryption (TDE) is an Enterprise-only feature, and attempting to enable it on Standard returns the error that TDE is not available in this version category. This is a common buyer trap, because TDE later became available in Standard starting with SQL Server 2019, so guides written for newer versions do not apply here. If you specifically need at-rest encryption of the whole database file on 2017, you must use Enterprise or upgrade to a 2019-or-later Standard license. Standard 2017 still supports cell-level encryption, Always Encrypted, row-level security, and dynamic data masking for more targeted protection.

Does SQL Server 2017 Standard require Client Access Licenses?

It depends on the licensing model: the Server plus CAL model requires a CAL for every user or device that accesses the server, while the per-core model requires no CALs at all. A SQL Server CAL must be the same version or newer than the server, so a 2017 server needs 2017-or-newer CALs, and one CAL lets that user reach multiple licensed SQL Server instances. The per-core model is the better fit when you cannot count users, run public-facing or extranet workloads, or expect access from external systems. For a fixed, countable internal user group, Server plus CAL is usually cheaper than licensing every physical core.

SQL Server Core Licensing and Minimum Requirements
How core minimums work and how to avoid the most common incorrect SQL Server purchases.

What should users check before choosing SQL Server 2017 Standard?

Confirm your workload stays under 24 cores and 128 GB of engine memory, because these are hard ceilings that Standard will not exceed even on larger hardware. Check whether you need Always On availability groups with readable secondaries or online index rebuilds, since both are Enterprise-only and cannot be added to Standard later. Verify your high-availability plan fits basic availability groups (one database, two replicas) or a two-node failover cluster. Finally, decide between per-core and Server-plus-CAL licensing up front, as switching models after deployment usually means repurchasing licenses.

Frequently asked questions about Microsoft SQL Server 2017 Standard

Can SQL Server 2017 Standard run on Linux?

Yes. SQL Server 2017 was the first release to support Linux distributions such as Red Hat, SUSE, and Ubuntu, as well as Docker containers, using the same Database Engine as the Windows build. This lets teams run the licensed Standard engine on existing Linux infrastructure without changing edition.

What is the maximum database size in SQL Server 2017 Standard?

A single relational database can grow to 524 PB, the same ceiling as Enterprise. In practice the real constraint is the 128 GB buffer pool memory limit, not file size, so very large active datasets will be paged from disk rather than held in memory.

Does SQL Server 2017 Standard include Always On availability groups?

Standard includes basic availability groups, which protect a single database with two replicas, plus two-node failover cluster instances. Full Always On availability groups with multiple readable secondaries are Enterprise-only, so multi-database or read-scale setups require Enterprise.

Are older SQL Server CALs compatible with a 2017 Standard server?

No. A SQL Server CAL must match or exceed the server version, so a 2017 server needs 2017-or-newer CALs; older 2014 or 2016 CALs do not grant access. The same CAL can, however, be used to reach multiple licensed SQL Server instances across editions.