database · reference

🐧

SQL Server 2017

SQL Server 2017 — first SQL Server on Linux, adaptive query processing, graph data, Python machine learning services.

← All products Licensing FAQ

On this page

Editions · channels · activation · audit notes · FAQs

Editions covered

—

Edition matrix with feature differences and the right audience.

In-depth sections

Channels, activation, audit, modern management & more.

FAQs answered

Common questions buyers and IT admins ask before purchase.

Words of reference

0.3k

Plain-English, no vendor agenda, updated to current Product Terms.

Deep dive

SQL Server 2017 — what to actually know

SQL Server 2017 shipped in October 2017 and was a landmark release: the first SQL Server engine to run on Linux (Red Hat, SUSE, Ubuntu) and inside Docker containers, with effectively identical T-SQL surface area as the Windows build. It introduced adaptive query processing, graph data support (nodes and edges as first-class table types), Python integration in Machine Learning Services (R was already in 2016), resumable online index rebuilds and automatic database tuning. Mainstream support ended 11 October 2022; extended support runs to 12 October 2027.

Editions and Linux specifics

Same edition stack as 2019: Enterprise, Standard, Web, Developer, Express. On Linux, the installer is a package (rpm / deb) and the service runs under systemd. Feature parity with the Windows build is high but not total — Filestream, distributed transactions across instances, and System Center management agents are Windows-only. The Docker image is officially supported for production on Linux hosts; for Windows hosts Microsoft recommends the native Windows installer.

Licensing

Per-core (Enterprise; Standard) or Server+CAL (Standard). Linux deployments are licensed the same way as Windows deployments — the operating system underneath does not change the SQL Server licence. Containers are licensed per physical core of the host when running on a host with unlimited virtualisation rights, otherwise per allocated vCore.

Support and upgrade path

Mainstream support ended October 2022. Extended support continues through 12 October 2027, with security patches but no new features. Direct in-place upgrade is supported to SQL Server 2019, 2022 and 2025. Customers running on Linux should plan a parallel upgrade of the underlying distribution at the same time, since RHEL/SUSE versions supported by 2017 are themselves moving out of support.

By channel

Where to buy this product

Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.

Channel fit (typical buyer)

Retail / FPP1

Volume Licensing10

CSP / Azure8

Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.

Support timeline

Lifecycle phases to plan against

SQL Server is the most expensive product Microsoft sells per core. Edition, core count and licensing model (per-core vs Server+CAL) have life-changing cost implications — model them before you buy.

Phase 1

General availability

Launch

Standard, Enterprise and Developer editions release simultaneously. Developer is free for non-production.

Phase 2

Mainstream support

5 years

Cumulative updates roughly every two months, plus security fixes. New feature work lands here.

Phase 3

Extended support

Years 5–10

Security-only servicing. No new TLS ciphers, no new features. SA required for non-security hotfixes.

Phase 4

ESU

Years 10–13

Up to 3 years of paid Extended Security Updates, or free ESU when the workload is moved to Azure SQL or an Azure VM.

Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

License every physical core on every server that runs SQL, with the 4-core-per-instance minimum and 2-pack increments.

DON'T

License only one VM's worth of cores when the underlying host can re-schedule the VM to any other host — that is unlicensed mobility.

Use Developer Edition for every non-production environment — it is feature-equivalent to Enterprise and free.

DON'T

Run real workloads on Express past the 10 GB / 1 GB-RAM / single-socket limits — it silently caps and corrupts capacity planning.

Document HA topology: passive secondaries are free under SA, active secondaries (read replicas, ETL) are not.

DON'T

Assume Always On replicas are free — only one passive secondary per primary is included, and only with active SA.

Consider Azure SQL Managed Instance or Azure SQL Database for new workloads — licensing collapses into the service cost.

DON'T

Buy Enterprise cores for a workload that fits comfortably in Standard — the price gap is large and Standard now covers most mid-market needs.

Typical deployments

How buyers actually use SQL Server 2017

Three reference deployments — find the closest match and adapt rather than starting from zero.

Scenario 1

Line-of-business ERP

Standard per-core on the active node, passive HA secondary covered by SA, regular backups to Azure Blob. Enterprise only if the ERP genuinely needs partitioning or in-memory OLTP.

Scenario 2

Data warehouse / BI

Enterprise per-core for columnstore at scale and advanced security. Consider Microsoft Fabric or Azure Synapse for greenfield analytics rather than scaling SQL Server vertically.

Scenario 3

ISV embedding SQL

Either bundle Express (with its caps) for free distribution, or buy SQL through the ISV royalty programme; never silently ship Developer Edition in a commercial product.

Cost optimisation

Where the savings actually live

None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.

💰

Standard wins for most mid-market apps

Standard covers 128 GB of buffer pool memory and most BI features. Reserve Enterprise for in-memory OLTP, advanced security, transparent data encryption at scale, or large data-warehouse workloads.

📊

Free passive secondary

With active SA, one passive HA replica per licensed primary is free. Plan your Always On topology to take advantage of this before adding paid secondaries.

🎯

Azure SQL for elastic workloads

Variable workloads (dev/test, reporting bursts, multi-tenant SaaS) collapse total cost in Azure SQL serverless or elastic pools versus statically licensed cores.

Counterfeit & risk

Red flags when buying second-hand

These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.

⚠ 01

Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.

⚠ 02

Lifetime key with no invoice or VLSC record

Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.

⚠ 03

Key works once, then 'not genuine' after the next cumulative update

Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.

⚠ 04

Seller refuses to put the entitlement in your tenant

Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

VLSC

Volume Licensing Service Center — the portal where Volume Licensing keys, agreements and downloads live.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →

FAQ

Frequently asked questions

Is this product still supported by Microsoft?+

Mainstream support ended 11 October 2022; extended support 12 October 2027. After extended support ends, no security updates are released through public Windows Update and the only path to continued patches is the Extended Security Updates (ESU) programme where Microsoft offers it. Running an unsupported version in production is a documented audit and compliance risk.

Is SQL Server 2017 on Linux still supported?+

Yes — until 12 October 2027 under extended support. New Linux distributions added after 2017 may not be officially supported even if the engine runs; check the Microsoft compatibility matrix.

Where can I legitimately buy a license?+

Through Microsoft's Retail channel (where the SKU is still sold), an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. For end-of-sale products, second-user (transferred) Volume Licensing through a documented chain of custody is the only legitimate secondary market.

What gets checked in a Microsoft licensing audit?+

Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail packaging), verify edition alignment, and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Older products are audited the same way as current ones — being out of mainstream support does not waive the licensing obligation.

Other products in this category

🗄️

SQL Server 2025

SQL Server 2025 — editions, per-core vs Server+CAL, Azure-connected features and Software Assurance benefits.

Read reference →

🗄️

SQL Server 2022

SQL Server 2022 — Azure-connected hybrid features, per-core and Server+CAL licensing, Standard vs Enterprise vs Developer.

Read reference →

🗄️

SQL Server 2019

SQL Server 2019 — Big Data Clusters, intelligent query processing, per-core and Server+CAL licensing.

Read reference →