<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Microsoft SQL Server 2022 Standard?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Database Engine</strong> – Runs relational OLTP and reporting workloads.<br /><strong>BI Services</strong> – Includes Reporting, Analysis, and Integration Services.<br /><strong>Built-in Security</strong> – TDE, Always Encrypted, and backup encryption.<br /><strong>Basic Availability</strong> – Two-node failover clustering and basic Always On.<br /><strong>Two Licensing Models</strong> – Choose Per Core or Server plus CAL.<br /><strong>Core Capacity</strong> – Engine capped at 24 cores, 128 GB RAM.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Microsoft SQL Server 2022 Standard?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SQL Server 2022 Standard is the mid-tier edition of Microsoft's relational database platform, built for departmental and mid-sized business workloads. It runs the same database engine as Enterprise but applies fixed core and memory ceilings to keep licensing cost predictable.<br /><br /><strong>Cost Control</strong> – Server plus CAL suits low user counts.<br /><strong>Full Database Size</strong> – Stores relational data up to 524 PB.<br /><strong>Practical High Availability</strong> – Failover clustering keeps a single instance online.<br /><strong>Modern T-SQL</strong> – Supports JSON, ledger tables, and time series.<br /><strong>Azure Connectivity</strong> – Links to Azure SQL Managed Instance for failover.<br /><strong>Component Bundle</strong> – One server license covers all SQL services.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does Microsoft SQL Server 2022 Standard do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SQL Server 2022 Standard hosts relational databases for transactional applications, internal reporting, and line-of-business systems. It uses the identical core engine found in Enterprise, so query syntax, T-SQL surface, and database file formats are fully compatible across editions. The difference is scale: the engine is restricted to the lesser of 4 sockets or 24 cores and 128 GB of buffer pool memory per instance. For a typical departmental OLTP database or an internal reporting server, those ceilings are rarely the bottleneck. You also get Integration Services for ETL jobs and Reporting Services for paginated reports under the same license.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Who is SQL Server 2022 Standard best suited for?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SQL Server 2022 Standard fits businesses running OLTP databases or departmental reporting that stay under 24 cores and 128 GB of RAM per instance. The Server plus CAL model becomes cheaper than per-core licensing for internal apps with a known, relatively low user count, often below roughly 100 to 130 users. It is a poor fit for public-facing websites where you cannot count users, since per-core then becomes mandatory and the core ceiling can be reached faster. A team that needs read-scale replicas or online index rebuilds during business hours should plan for Enterprise instead, because Standard performs index rebuilds offline.</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 2017–2025 Buying Guide: License Models and CALs</strong><br />How to compare Per Core and Server plus CAL licensing and pick the right SQL product for your user count.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">How does SQL Server 2022 Standard compare to Enterprise?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Standard and Enterprise share the same engine, but Enterprise removes the scale ceilings and adds high-end availability and performance features. Standard tops out at 24 cores and 128 GB of engine memory, supports only Basic Availability Groups (two replicas, one database) and a two-node Failover Cluster Instance, and rebuilds indexes offline. Enterprise allows OS-maximum cores and memory, advanced Always On with up to eight secondary replicas, readable secondaries, online index operations, and Resource Governor. Both editions support the same 524 PB maximum database size and identical T-SQL, so an application built on Standard runs unchanged on Enterprise.</p>
<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 />Version-by-version comparison of engine features and edition differences across recent SQL Server releases.</a></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 2022</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">Enterprise 2022</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;">24 cores</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">OS max</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Max 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 max</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</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Advanced</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;">Resource Governor</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>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Server + CAL option</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;">Per core only</td>
</tr>
</tbody>
</table>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the core licensing requirements for SQL Server 2022 Standard?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Under the Per Core model you must license every physical core on the server, with a minimum of four core licenses per physical processor, and cores are sold in two-core packs. Per Core needs no CALs and allows unlimited users, which is why it is the only sensible model for public or external-facing databases. The alternative Server plus CAL model uses one server license plus a Client Access License for each connecting user or device. A practical trap: licensing by virtual cores assigned to a VM is only allowed with active Software Assurance or a subscription, so a plain perpetual core license must cover all physical cores on the host.</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 2017–2025: Core Licensing and Minimum Requirements</strong><br />How core minimums and two-core packs work, and how to avoid buying the wrong number of licenses.</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 biggest limits are the 24-core and 128 GB engine ceilings, plus offline-only index rebuilds, which lock a table during maintenance and can block business-hours operations. Standard supports only Basic Availability Groups, meaning two replicas tied to a single database with no readable secondary, so you cannot offload reporting reads to a passive replica. In-Memory OLTP is capped at 32 GB per database and columnstore batch-mode parallelism is limited to a degree of 2. Resource Governor is also absent, so you cannot cap CPU or memory per workload. If your workload depends on any of these, Enterprise is the correct edition rather than a workaround.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Frequently asked questions about SQL Server 2022 Standard</h3>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does SQL Server 2022 Standard require Client Access Licenses?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Only the Server plus CAL model requires CALs; the Per Core model does not and allows unlimited users. A SQL Server CAL must match or exceed the server version, so a 2022 CAL covers a 2022, 2019, or 2017 Standard server, and one CAL can access multiple licensed SQL Servers. For external-facing or high-user databases, choose Per Core to avoid counting users.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can SQL Server 2022 Standard run Always On Availability Groups?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, but only Basic Availability Groups, which allow two replicas and exactly one database per group. The secondary replica is not readable, so it cannot serve reporting queries while acting as a standby. For multi-database groups, readable secondaries, or more than two replicas you need Enterprise edition.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does SQL Server 2022 Standard include Reporting and Analysis Services?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, Reporting Services, Analysis Services, and Integration Services are all included under a single SQL Server license when run on the same server. If you install any of these components on a separate server, that machine must be fully licensed on its own. This matters when planning a dedicated ETL or reporting box, because it doubles the licensing requirement.</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 2017–2025 FAQ: Standard, Enterprise, and CALs</strong><br />Common buyer questions about edition differences, CAL rules, and choosing between Standard and Enterprise.</a></p>