Microsoft SQL Server 2017 Standard - 24 Core

# Microsoft SQL Server 2017 Standard - 24 Core

## Hook

Microsoft SQL Server 2017 Standard - 24 Core is for buyers who need a stable Microsoft database platform with a defined 24-core licence scope and a practical upgrade step beyond SQL Server 2016. It often fits SMEs, consultants, software vendors, branch offices, service companies, clinics, finance teams, and internal IT departments that run a real business application but do not need Enterprise edition. The database may sit behind a web portal, stock system, invoicing tool, reporting store, CRM connector, or vendor-certified line-of-business platform.

This listing is not Microsoft 365, not Azure SQL Database, not an Azure virtual machine charge, not Windows Server, not an OEM PC licence, not a KMS host, and not a bundle of Client Access Licences. It is a Microsoft SQL Server 2017 Standard licence offer for a 24-core scope. That clarity helps when the buyer is not a full-time database administrator but still needs to make a responsible purchase for a production system.

Lizensa frames the purchase around compatibility, activation, and records. You receive digital delivery where order checks and stock allow it, invoice documentation, and guidance for the supplied activation route. If you are comparing versions, review [Microsoft SQL Server 2016 Standard - 24 Core](/products/microsoft-sql-server-2016-standard-24-core), [Microsoft SQL Server 2019 Standard](/products/microsoft-sql-server-2019-standard), [Microsoft SQL Server 2022 Standard](/products/microsoft-sql-server-2022-standard), [Microsoft SQL Server 2025 Standard](/products/microsoft-sql-server-2025-standard), and the [SQL Server category](/categories/sql-server). For the operating system layer, [Windows Server 2022 Standard](/products/windows-server-2022-standard-16-core) is a separate decision.

## What you get

This product covers Microsoft SQL Server 2017 Standard with a 24-core licensing scope. Standard edition is the mainstream production choice for many departmental and SME workloads: application databases, reporting databases, small data marts, vendor back ends, internal platforms, and services that need SQL Server reliability without Enterprise edition cost or feature depth. It gives you a familiar database engine, mature administration patterns, backup and maintenance workflows, SQL Server Agent jobs, security controls, and broad application support.

The 24-core scope should be connected to the actual environment before activation. Document whether the database will run on a physical host, a virtual machine, a virtualisation cluster, or a replacement server. Record the core count, application name, database owner, technical owner, backup owner, deployment date, invoice, delivery email, activation notes, and support messages. This is not bureaucracy for its own sake. When a server is restored, moved, audited, upgraded, or handed to another administrator, those records prevent costly guessing.

SQL Server licensing can be per-core or Server plus CAL depending on product, agreement, and deployment. This SKU is written for a 24-core purchase. If you only need user or device access rights for a separately licensed server, look for CAL products. If you need managed database hosting, compare Azure SQL. If you need the Windows operating system, buy or confirm Windows Server separately.

## What's new

SQL Server 2017 is notable because it brought SQL Server strongly into Windows, Linux, and container deployment patterns. That does not mean every buyer should run it on Linux, but it widened the platform choices for teams that were modernising infrastructure. It also continued the security and performance direction of SQL Server 2016 with Query Store, Always Encrypted, Row-Level Security, Dynamic Data Masking, JSON support, and columnstore improvements, while adding capabilities such as graph database features and adaptive query processing.

For an SME buyer, the question is not whether every feature sounds impressive. The question is whether SQL Server 2017 is the certified and supportable generation for your application. If a vendor says SQL Server 2017 Standard is supported, it may be the right balance between staying older than a risky major upgrade and avoiding the stricter lifecycle pressure of SQL Server 2016. If your workload has no version constraint, newer releases such as SQL Server 2019 or 2022 may provide a better long-term baseline.

Choose this SKU when you need SQL Server 2017 Standard and can map the deployment to a 24-core target. Choose SQL Server 2016 if the application is locked to the previous generation. Choose SQL Server 2019 or 2022 when the application can be tested on a newer platform. Choose Enterprise when the workload clearly needs Enterprise-only features. Choose Azure SQL when you want managed cloud database consumption and are ready for the architecture change.

## System requirements

| Item | Requirement | | --- | --- | | Operating system | Supported Windows Server environment or supported Linux distribution for SQL Server 2017 | | Processor | x64 processor sized for database workload, concurrency, and reporting | | Memory | Plan RAM for the application, maintenance jobs, caching, and recovery goals | | Storage | Resilient storage for data, logs, tempdb, backups, and growth | | Network | Stable connectivity for clients, administration, monitoring, backup, and replication | | Internet | Required for digital delivery and may be required for activation or updates | | Included scope | Microsoft SQL Server 2017 Standard - 24 Core | | Licence model | Perpetual SQL Server software licence scope; no Microsoft 365 or Azure subscription included |

Do the practical checks before activation. Confirm operating system support, application certification, driver versions, collation, compatibility level, backup software, monitoring, service accounts, firewall rules, high-availability design, virtualisation placement, and restore testing. For systems holding personal data, document GDPR responsibilities, access rights, retention periods, backup encryption, and who approves database copies for testing.

## Comparison

| Option | Best fit | Main caution | | --- | --- | --- | | SQL Server 2017 Standard - 24 Core | Production workloads certified for SQL Server 2017 Standard with a measured 24-core target | Retest applications, drivers, and backup tooling before migration | | SQL Server 2016 Standard - 24 Core | Older systems locked to the 2016 generation | Shorter lifecycle runway and Windows-focused deployment assumptions | | SQL Server 2019 Standard | Newer baseline for many on-premises applications | Vendor certification may require testing | | SQL Server 2022 Standard | Longer modern runway and newer engine behaviour | More change for legacy workloads | | Azure SQL | Managed cloud database model | Subscription billing, migration work, and cloud design decisions |

SQL Server 2017 Standard can be a sensible middle point. It is newer than 2016 and supports broader platform patterns, but it is still familiar to many administrators and application vendors. It is not automatically the best choice for every new project. If your business is building a fresh system, compare newer SQL Server releases and managed cloud options. If your business is stabilising an existing application, the version certified by that application should carry more weight than a generic feature list.

Lizensa supports this decision with product-level clarity, digital fulfilment, invoice records, EU-focused support, GDPR-conscious order handling, and a practical 365-day activation guarantee for eligible activation issues within the supplied scope.

## Install + activation

After checkout, open the Lizensa delivery email and confirm the exact product, edition, language, core scope, and activation route. Decide whether this is a new deployment, an in-place replacement, a side-by-side migration, or a disaster-recovery rebuild. Prepare the server, operating system, storage layout, service accounts, firewall rules, backup destination, monitoring route, and administrator access before starting setup.

Install only the components needed for the workload. Apply current cumulative updates, install SQL Server Management Studio where needed, configure authentication, set memory limits deliberately, place data, log, and tempdb files sensibly, and create backup, CHECKDB, index, statistics, alerting, and monitoring jobs before production use. Test restore, not only backup. Keep the Lizensa invoice, delivery email, activation notes, server inventory, core evidence, and deployment notes in one location.

EU digital-content rules also matter. The 14-day withdrawal right can depend on consent to immediate delivery and whether activation has started, while statutory rights remain if the product is not delivered as described. Do not activate until the edition, version, and deployment scope are correct.

## FAQ

### Is Microsoft SQL Server 2017 Standard - 24 Core a subscription? No. It is positioned as a perpetual SQL Server software licence scope for the listed 24-core product, not Microsoft 365 or Azure consumption.

### Does it include Windows Server? No. SQL Server and Windows Server are separate products. Confirm the operating system licence separately.

### Does it include CALs? Do not assume that. This listing is written around a 24-core SQL Server scope, not a separate CAL pack.

### Is this OEM, MAK, KMS, or Azure? Treat it as a SQL Server software licence listing with the supplied activation route. It is not Azure SQL and not a KMS host.

### Can I deploy SQL Server 2017 on Linux? SQL Server 2017 supports selected Linux deployment scenarios, but you must confirm the exact distribution, vendor support, drivers, and operational tooling before deployment.

### Who should choose Standard instead of Enterprise? Choose Standard when the workload fits Standard edition limits. Choose Enterprise only when scale, availability, resource governance, or Enterprise-only features are required.

### What should I check before activation? Check edition, version, core count, application certification, operating system support, virtualisation design, backup plan, restore testing, monitoring, and internal licence policy.

### What if activation fails? Check the product edition, server connectivity, entered key, existing installations, and exact error message. Then contact Lizensa with the order number, screenshots, and activation step.

## Related products

- [SQL Server category](/categories/sql-server) - [Microsoft SQL Server 2016 Standard - 24 Core](/products/microsoft-sql-server-2016-standard-24-core) - [Microsoft SQL Server 2019 Standard](/products/microsoft-sql-server-2019-standard) - [Microsoft SQL Server 2022 Standard](/products/microsoft-sql-server-2022-standard) - [Microsoft SQL Server 2025 Standard](/products/microsoft-sql-server-2025-standard) - [Windows Server 2022 Standard](/products/windows-server-2022-standard-16-core) - [Microsoft Visual Studio Professional 2022](/products/microsoft-visual-studio-professional-2022-2-users)