How to fix Error 3622 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: Error 3622 — Invalid Floating Point Operation in SQL Server 2025

Why This Error Happens

Error 3622 occurs when SQL Server’s query processor encounters an invalid floating-point operation—such as an overflow, underflow, or a computation producing NaN (Not a Number)—typically during arithmetic operations on float or real data types. This is frequently triggered by corrupted data pages, a damaged database following an improper shutdown, or queries that perform mathematical operations (like division, exponentiation, or aggregate functions) on values that exceed the valid range for the floating-point data type. In some cases, this error surfaces due to underlying storage corruption or hardware-level memory errors affecting the data at rest.

Step-by-Step Resolution Guide

Step 1: Run DBCC CHECKDB to Identify Corruption

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Execute the following command against the database reporting the error:
DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Review the output for allocation or consistency errors, particularly around pages containing float or real columns.
  • If corruption is confirmed, note the affected table and index IDs for targeted repair.

Step 2: Isolate the Offending Query or Column

  • Use SQL Server Profiler or Extended Events to capture the exact query triggering Error 3622.
  • Check the query execution plan for operations involving CAST, CONVERT, POWER, LOG, EXP, or division on float/real columns.
  • Temporarily rewrite the query using TRY_CAST or TRY_CONVERT to isolate whether the issue is data-driven rather than storage corruption:
SELECT TRY_CAST(YourColumn AS float) FROM YourTable;
  • Cross-reference flagged rows against expected value ranges for float (approximately ±1.79E+308) and real (±3.40E+38).

Step 3: Repair or Restore Affected Data

  • If DBCC CHECKDB flagged corruption, run a repair option matching the severity:
DBCC CHECKDB ('YourDatabaseName') WITH REPAIR_REBUILD;
  • If data loss is deemed acceptable only as a last resort, use REPAIR_ALLOW_DATA_LOSS in a single-user mode session.
  • If corruption is extensive, restore the database from the most recent verified-clean backup instead of running repair commands.
  • Validate the underlying storage subsystem using chkdsk on Windows Server 2025 and review the Windows Event Viewer for Disk or NTFS-related warnings.

Step 4: Update SQL Server 2025 Cumulative Updates

  • Navigate to the Microsoft Update Catalog and confirm the instance is on the latest Cumulative Update (CU) for SQL Server 2025.
  • Apply the update via SQL Server Installation Center or Windows Update, ensuring the service is stopped beforehand through SQL Server Configuration Manager.
  • Restart the SQL Server service and re-run the original query that triggered Error 3622.

Alternative or Verification Steps

  • After applying fixes, re-execute DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS; and confirm zero allocation or consistency errors are returned.
  • If the error persists only on specific queries, replace raw float/real arithmetic with the decimal or numeric data type, which does not produce invalid floating-point exceptions under the same overflow conditions.