Activating Microsoft SQL Server 2019 Standard

This guide is exclusively about activating the licence for Microsoft SQL Server 2019 Standard. It does not describe the engine installation or instance configuration. In practice, activating SQL Server usually means entering a valid product key into an already installed instance or performing an Edition Upgrade from the Evaluation/Developer version to Standard.

When Activation is Needed

Activation is typical in several situations:

• after deploying a trial version and switching to the Standard edition,
• after purchasing a new product key,
• after restoring a server from a backup or migration,
• after changing hardware or a virtual machine,
• when a previously used key is no longer accepted.

Important: in the case of SQL Server, slmgr.vbs /ipk or slmgr.vbs /ato are not used. These are tools for the Windows/Windows Server system, not for the SQL Server engine. Activating SQL Server 2019 Standard is done through the SQL Server installer mechanism.

Activating with a Product Key in the GUI

The most convenient method is to use the Edition Upgrade wizard:

1. Open the SQL Server Installation Center.
2. Go to the Maintenance section.
3. Select Edition Upgrade.
4. Specify the instance you want to activate.
5. Enter the 25-character product key for SQL Server 2019 Standard.
6. Accept the licence terms.
7. Complete the wizard and restart the SQL Server service if the installer requires it.

This method is suitable when the server is already running as an Evaluation or requires the assignment of a commercial edition.

Activating with a Product Key from the Command Line

If you prefer a text-based mode or work remotely, use the installer with the EditionUpgrade parameter.

For the default instance:

setup.exe /Q /ACTION=EditionUpgrade /INSTANCENAME=MSSQLSERVER /PID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /IACCEPTSQLSERVERLICENSETERMS

For a named instance, e.g. SQL2019:

setup.exe /Q /ACTION=EditionUpgrade /INSTANCENAME=SQL2019 /PID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /IACCEPTSQLSERVERLICENSETERMS

If you run the command from an ISO medium, first navigate to the directory with setup.exe. After completion, check the installer logs in the directory:

C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\

Telephone Activation: 00 800 121 1654

SQL Server does not have a separate telephone activation wizard like older Windows versions, but the telephone activation and reactivation path is used when:

• the key is rejected despite correct syntax,
• the number of activations has been exhausted,
• the licence was already assigned to another server,
• significant hardware changes have been made,
• manual verification of entitlement is required.

Microsoft contact number: 00 800 121 1654

Before the call, prepare:

• the full product key,
• the product name: Microsoft SQL Server 2019 Standard,
• information on whether the activation concerns a physical server or a VM,
• a description of the hardware change or migration,
• proof of purchase or order number, if you have it.

For assistance with KluczeSoft products, please contact [email protected].

Activation Verification

In SQL Server, there is no equivalent of slmgr /xpr. Verification is performed by confirming that the instance is already running as Standard Edition.

sqlcmd — precise command

sqlcmd -S localhost -E -Q "SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS ProductVersion, SERVERPROPERTY('ProductLevel') AS ProductLevel;"

For a named instance:

sqlcmd -S localhost\SQL2019 -E -Q "SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS ProductVersion, SERVERPROPERTY('ProductLevel') AS ProductLevel;"

Additional version control

sqlcmd -S localhost -E -Q "SELECT @@VERSION AS VersionInfo;"

The correct result should indicate Standard Edition. If you still see Evaluation or Developer Edition, activation has not been applied to this instance.

Activation Troubleshooting

Below are the most common, real errors related to activation and edition change:

• 0x84B10001 — incorrect product key. Most often a typo, a key from a different version or edition.
• 0x84C40013 — the selected key does not match the operation being run or the instance. Check if you are using EditionUpgrade, not another setup action.
• 0x84B40000 — validation error during installer startup. Often results from incomplete media files or running from the wrong directory.
• 0x84C4000D — the operation cannot be completed for the specified instance. Occurs when there is a mistake in the instance name.
• 0x84B20002 — setup cannot read or apply parameters. Check the command syntax and completeness of switches.
• 0x84BB0001 — internal setup error or component conflict. It's worth running the wizard again after restarting the server.
• -2061893606 — general SQL Server Setup error, often seen in logs with a failed edition change; requires analysis of Detail.txt and Summary.txt files.

If an error occurs, always check the logs in:

C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\

What to do when the key does not work

If the key is rejected:

1. Check if it's indeed the key for SQL Server 2019 Standard, not for another version or edition.
2. Ensure you are activating the correct instance.
3. Verify that the key has not been used beyond the allowed limit.
4. Try again through the GUI, and if that doesn't help, through CMD.
5. Contact Microsoft at 00 800 121 1654 and prepare proof of purchase.
6. If the key comes from a reseller, ask for re-verification of the license source or key exchange.

Reactivation after hardware change

After replacing the motherboard, VM migration, changing the host, or restoring the server, reactivation may be necessary. The safest path:

1. Run Edition Upgrade again with the same key.
2. Verify the edition with the sqlcmd command.
3. If the key is rejected as already used, use the phone 00 800 121 1654.
4. During the conversation, explain that it's a reactivation after hardware change, not a new, additional installation.

CAL and activation

CAL licenses are not activated with a key in SQL Server. CAL is a license document / legal entitlement, not a code entered into the wizard. The server itself is activated with a product key for the edition, while CAL accounts for the legal access of users or devices.

Summary

Activating Microsoft SQL Server 2019 Standard involves assigning a valid product key to the instance, usually through Maintenance > Edition Upgrade or the command setup.exe /ACTION=EditionUpgrade /PID=.... The correctness of the activation is best confirmed by the sqlcmd command checking SERVERPROPERTY('Edition'). If the key does not work, it has been blocked or reactivation is required after a hardware change, the proper escalation path is to contact Microsoft at 00 800 121 1654.