Teams deploying in mid-2026 often choose SQL Server 2025 Standard Edition because the edition now supports up to 32 cores and 256 GB of buffer pool memory per instance, along with Resource Governor. Those capacity increases make Standard viable for workloads that previously required Enterprise. The first real friction surfaces before anyone launches setup.exe. Licensing decisions determine whether the deployment stays compliant and whether the architecture needs to change.

Licensing SQL Server 2025 Standard Edition in Current Deployments

Microsoft kept the core licensing model for both Standard and Enterprise in the 2025 release. Core licenses come in 2-core packs with a minimum of four cores per physical processor or per virtual machine. The edition also retains the Server + CAL option that Standard alone offers.

Per-core licensing counts the cores the operating system sees. On a physical server, you license every core in the machine. In a virtual machine, you license the vCores assigned to that guest, again with the four-core floor. Packs are sold in pairs, so a four-core minimum usually means buying at least one 2-pack and often more depending on rounding.

The rule that trips up the most teams concerns virtualization rights when Software Assurance is not purchased. Licensing all physical cores on a host without Software Assurance grants the right to run SQL Server in only one operating system environment. That OSE can be the physical host or a single virtual machine. It does not extend to additional virtual machines on the same host. Each extra VM requires its own set of core licenses covering its assigned vCores.

Consider a host with 16 physical cores running three virtual machines that each receive four vCores. Without Software Assurance, you cannot license the 16 cores once and place SQL Server instances in all three guests. You license each VM separately for its four vCores. The economics shift quickly, and the decision between consolidation and additional licenses must happen early in planning.

Software Assurance changes the picture. With SA or subscription licenses, you can license by virtual cores per VM while retaining reassignment flexibility within the licensed core count. Enterprise with SA still receives the unlimited virtualization benefit on a fully licensed host. Standard does not. Many organizations therefore evaluate the Server + CAL model when user counts stay low, roughly under 30 concurrent users or devices, because the crossover point often favors per-core once concurrency or core counts rise.

Power BI Report Server is now included with core licenses for both Standard and Enterprise. The Web edition no longer exists for 2025, though SQL Server 2022 Web remains supported until early 2033. These details matter when you map existing workloads to the new release.

When you source genuine licenses through standard enterprise channels, the reseller records the exact model and quantity. That record determines the product key format you receive and the activation path that follows. Keep the confirmation that lists whether the purchase was per-core or Server + CAL; it prevents mismatches later.

Acquiring the License and Media

Digital delivery arrives as an email with the 25-character product key and instructions, or as portal access to the Volume Licensing Service Center for volume agreements. The media itself is usually the same ISO regardless of edition; the key selects Standard during setup. Verify the SHA256 hash Microsoft publishes for the download when the file is large.

Some teams still request the Evaluation edition first for proof-of-concept, then convert to licensed media by entering the purchased key. The conversion works cleanly provided the target edition matches the key type. A Standard key applied to Enterprise media typically fails or installs a limited feature set.

Pair the SQL Server 2025 Standard license with Windows Server 2025 Standard or Datacenter from the same channel when possible. Unified support terms and matching patch cycles reduce friction during the first year of operation.

Preparing the Target Server

SQL Server 2025 installs on Windows Server 2019 and later, including Windows Server 2025. Windows Server 2025 with the Server Core installation option remains the recommended production base for security surface reduction. The wizard runs on both Core and Desktop Experience.

Minimum hardware stays modest: x64 processor at 1.4 GHz or faster, 1 GB RAM for non-Express editions, and 6 GB free disk space. Production deployments use at least 8–16 GB RAM and separate volumes for data, log, tempdb, and backups. Disks with 4 KB or 512-byte sectors are preferred. Larger sector sizes trigger a registry workaround documented in the I/O basics whitepaper; apply it before install if your storage array presents 8 KB or larger sectors.

Install the latest Windows updates and the .NET Framework 4.7.2 prerequisite. Disable the domain controller role on the target machine. SQL Server services cannot run under local accounts on domain controllers, and failover clustering is unsupported there as well.

Create dedicated service accounts or use group Managed Service Accounts for the SQL Server and SQL Server Agent services. gMSAs remove password management while satisfying domain policies that many organizations enforce in 2026.

Running the Installation Wizard

Mount the ISO or launch setup.exe from the extracted folder. The SQL Server Installation Center opens.

Select Installation on the left, then New SQL Server standalone installation or add features to an existing installation.

On the Product Key page, paste the 25-character key received from digital delivery. The wizard validates the format immediately. If the key belongs to a volume agreement, it may show as “Volume License” and skip some retail-specific prompts.

Accept the license terms. Choose whether to use Microsoft Update for setup files and later patches. Most production teams enable it and then control broader update rings through WSUS or Azure Update Manager.

The wizard installs setup support files. Next comes the feature selection tree. For a typical Standard Edition OLTP or mixed workload, select:

• Database Engine Services
• SQL Server Replication (if merge or transactional replication is planned)
• Full-Text and Semantic Extractions for Search (when text-heavy queries are expected)
• SQL Server Agent (installed automatically with the engine in most cases)

Leave PolyBase, Analysis Services, and Reporting Services unchecked unless the workload specifically requires them. Resource Governor is now available in Standard and appears under the engine options once selected.

On the Instance Configuration page, choose Default instance for single-instance servers or supply a named instance when multiple named instances will coexist. Named instances require unique port assignments later.

Server Configuration lets you set service accounts and startup types. Use the gMSA or domain account created earlier. Set SQL Server Agent to Automatic. Collation defaults to SQL_Latin1_General_CP1_CI_AS; change only when application requirements dictate a different sort order or case sensitivity.

Database Engine Configuration is where most production decisions live. Select Mixed Mode if applications or users need SQL Server authentication in addition to Windows authentication. Add the current Windows account plus any dedicated DBA accounts to the SQL Server administrators list. Specify non-C: paths for data root, user database, log, tempdb, and backup directories. Place tempdb on its own fast volume with multiple data files sized equally; eight files is a common starting point for 16-core systems.

The wizard summarizes everything on the Ready to Install page. Review the feature list and directory paths one final time. Click Install. The process takes 15–40 minutes depending on selected features and disk speed.

Entering the Digital License Key and Activation

The product key entered during the wizard determines the edition. After installation completes, verify with a quick SQL query:

SELECT SERVERPROPERTY('Edition') AS Edition,
       SERVERPROPERTY('ProductVersion') AS Version,
       SERVERPROPERTY('EditionID') AS EditionID;

If the edition shows correctly, activation usually completes automatically when the server has outbound internet access. Firewalls that block the activation endpoints require an exception or an offline activation workflow supplied with volume licenses.

For air-gapped environments or KMS setups, use the Volume Activation tools or the phone activation option presented during first connection attempts. Document the confirmation ID returned by Microsoft; it pairs with the installation ID generated on the server.

Teams that receive keys through authorized resellers rarely encounter “key already in use” errors when the purchase record is clean. If activation still fails, the reseller support channel can confirm the key status against the Microsoft backend within minutes.

Post-Installation Verification and Hardening

Apply the latest Cumulative Update immediately after a successful install. As of June 2026, several CUs have been released for the 17.x branch; install the most recent one that matches your build.

Run the following checks:

• Confirm all SQL Server services are running under the expected accounts.
• Open SQL Server Configuration Manager and enable TCP/IP if Named Pipes alone was selected.
• Add firewall rules for the instance port (default 1433) or the dynamic port range if using named instances.
• Set max server memory to 75–80 % of physical RAM minus 4–8 GB for the OS, using sp_configure.
• Move tempdb files off the C: drive if the wizard default was accepted.

A short natural digression that surfaces in almost every production review: the four-core minimum still applies even when a small VM receives only two vCPUs for cost control. You license and pay for four cores regardless. That detail forces an early conversation between infrastructure and finance teams before any VM is provisioned.

Common Gotchas Teams Encounter in 2026

Core count mismatches appear when hypervisor tools report logical processors instead of assigned vCores. Always use the VM settings panel or PowerShell to confirm the exact vCPU count presented to the guest.

Edition downgrade attempts after install fail. If the wrong media was used, reinstall with the correct key rather than trying to edit registry values.

Sector size warnings on modern NVMe or SAN storage can be ignored during the wizard but should be addressed with the ForcedPhysicalSectorSizeInBytes registry key before production workloads begin.

Mixed-mode authentication left enabled without auditing creates unnecessary attack surface. Review the SQL Server logs and consider contained database users or Azure AD integration for new applications.

Multiple instances on one host require unique instance names and non-overlapping ports. Document each instance’s port and service account before handing the server to operations.

Next Operational Steps

Once verification and the first Cumulative Update are complete, the immediate priorities become baseline performance capture, backup strategy implementation, and connection string testing from the application tier. Those tasks sit outside the installation itself yet depend directly on the licensing model and feature choices made during setup. Get those two elements right and the rest of the deployment proceeds on stable ground.