<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Microsoft SQL Server 2019 Standard?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Database Engine</strong> – Full relational engine for transactional and reporting workloads.<br /><strong>Basic Availability Groups</strong> – Two-replica failover protection for a single database.<br /><strong>Failover Clustering</strong> – Two-node instance clustering for hardware redundancy.<br /><strong>TDE Encryption</strong> – Transparent Data Encryption protects data files at rest.<br /><strong>Core Capacity</strong> – Lesser of 4 sockets or 24 cores, 128 GB RAM.<br /><strong>Important</strong> – Client Access Licenses (CALs) are not included in this edition.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Microsoft SQL Server 2019 Standard?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SQL Server 2019 Standard is the mid-tier relational database for departmental applications, line-of-business systems, and data marts that stay within 24 cores and 128 GB of engine memory. It runs the same query engine as Enterprise but caps scale and advanced availability features.<br /><br /><strong>Cost Control</strong> – Standard pricing for workloads under engine limits.<br /><strong>Cross Platform</strong> – Installs on Windows, Linux, and Docker containers.<br /><strong>Built-in Security</strong> – TDE, Always Encrypted, and row-level security included.<br /><strong>Basic Failover</strong> – Two-replica availability groups guard one critical database.<br /><strong>No Size Cap</strong> – Relational databases scale to 524 PB.<br /><strong>Backup Compression</strong> – Shrinks backup files and shortens backup windows.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/optimized-data-management-with-sql-server-40-discount-until-march-31-2025" target="_blank"><strong>SQL Server 2017 to 2025: Editions and License Selection Compared</strong><br />Buying advice covering differences, features, editions, support timelines, and how to choose the right license.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does Microsoft SQL Server 2019 Standard do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It stores, queries, and protects relational data using the same core Database Engine found in Enterprise, with hardware scale capped at the lesser of 4 sockets or 24 cores and 128 GB of buffer-pool memory. In practice this handles OLTP applications, ERP back-ends, and reporting databases for small and mid-sized deployments. SQL Server 2019 Standard also runs natively on Linux and in Docker containers, so you can host the same instance on a Windows VM or a Linux host without changing edition. It includes the in-database engine plus tools such as SQL Server Agent for scheduled jobs and maintenance.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Who is Microsoft SQL Server 2019 Standard best suited for?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It fits organizations whose busiest single instance stays under 24 cores and 128 GB of engine memory, which covers most departmental and line-of-business databases. A team running an accounting or inventory system that needs scheduled backups, basic redundancy, and encryption at rest gets all of that without paying for Enterprise. The 128 GB buffer-pool ceiling is the practical decision point: workloads that regularly read more than that into memory will see paging and slower queries that Enterprise would avoid. If you need only one protected database and can tolerate a two-replica failover model, Standard removes the cost of features you would not use.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">How does SQL Server 2019 Standard compare to Enterprise edition?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Standard runs the same Database Engine as Enterprise but caps compute at the lesser of 4 sockets or 24 cores and buffer-pool memory at 128 GB, while Enterprise scales to the operating system maximum. The biggest functional gap is high availability: Standard supports only Basic Availability Groups (two replicas, one database, no readable secondary), whereas Enterprise allows multiple readable replicas and multi-database groups. Standard also omits online index rebuilds, table partitioning performance benefits, and Resource Governor, which matters for large always-on systems doing maintenance without downtime. For mid-tier workloads inside the scale limits, the engines behave identically, so the choice comes down to scale and availability needs.</p>
<table style="width: 100%; border-collapse: collapse; background-color: #efefef; margin-top: 15px; margin-bottom: 15px; font-size: 14px; line-height: 1.35;">
<tbody>
<tr><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: left; font-weight: bold; background-color: #dedede;">Feature</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">Standard</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">Enterprise</th></tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Max cores</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">4 sockets / 24 cores</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">OS maximum</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Engine memory</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">128 GB</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">OS maximum</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Max database size</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">524 PB</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">524 PB</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Always On AG</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Basic only</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Failover cluster nodes</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">2 nodes</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">16 nodes</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Online index rebuild</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">TDE encryption</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
</tbody>
</table>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2022-2019-and-2017-features-and-differences" target="_blank"><strong>SQL Server 2022, 2019, and 2017: Features and Differences</strong><br />Side-by-side comparison of what each version added, removed, and changed across editions.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What technical limitations should users know before buying?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">The hard ceilings are 24 cores, 128 GB of engine memory, and a single database per Basic Availability Group with no readable secondary replica. Standard also lacks online index rebuilds and table partitioning performance features, so large index maintenance requires taking objects offline during a window. In-memory OLTP is allowed but capped at 32 GB per database, far below the unlimited Enterprise allowance. Check your peak working-set size first: if queries routinely need more than 128 GB cached, Standard will page to disk and you will not get the throughput Enterprise delivers on the same hardware.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2017-2025-core-licensing-minimum-requirements-and-incorrect-purchases" target="_blank"><strong>SQL Server Core Licensing and Minimum Requirements Explained</strong><br />How core counts, four-core minimums, and edition limits affect what you actually need to buy.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does SQL Server 2019 Standard require additional Client Access Licenses (CALs)?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It depends on the licensing model: under the Server + CAL model each user or device connecting to the server needs a SQL Server CAL, and those CALs are not included with this edition unless your package explicitly bundles them. Under the per-core model there is no user or device counting and no CAL requirement, but every physical core on the server must be licensed with a minimum of four cores per processor. A SQL Server CAL must be the same version or newer than the server, so a 2019 CAL can access a 2019 instance and older servers, but a 2017 CAL cannot legally access 2019. Choose per-core when you cannot count users or run internet-facing workloads, and Server + CAL when user counts are small and known.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/sql-server-2017-2025-buying-guide-how-to-understand-license-models-cals" target="_blank"><strong>SQL Server Buying Guide: License Models and CALs</strong><br />How to read the per-core and Server + CAL models and pick the right SQL product.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does SQL Server 2019 Standard support full Always On Availability Groups?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. Standard supports only Basic Availability Groups, which protect one database with a single secondary replica and no read access on that secondary. Full Always On Availability Groups with multiple readable replicas and multi-database failover are exclusive to Enterprise edition. If you need to offload read traffic or fail over several databases together, Basic Availability Groups will not cover it, and the documented Read-Scale option does not work on Standard despite earlier documentation errors. For most departmental systems with one critical database, the two-replica Basic model is enough to meet a recovery-point objective.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Frequently asked questions about Microsoft SQL Server 2019 Standard</h3>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can SQL Server 2019 Standard run on Linux?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes. SQL Server 2019 Standard runs on Windows, supported Linux distributions, and Docker containers using the same Database Engine. The same edition limits apply regardless of platform.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">How long is SQL Server 2019 supported?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Mainstream support has ended, and extended support runs until January 8, 2030. During extended support you still receive security updates but not new feature changes.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Is in-memory OLTP available in Standard edition?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, but it is limited to 32 GB of memory-optimized data per database. Enterprise has no fixed cap beyond available memory, so very large in-memory tables need Enterprise.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/buying-guide-sql-server-2017-to-2025-faq-frequently-asked-questions-about-standard-enterprise-and-ca" target="_blank"><strong>SQL Server FAQ: Standard, Enterprise, and CALs</strong><br />Common buyer questions about edition differences and CAL requirements answered in one place.</a></p>