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

by

Troubleshooting Guide: SQL Server Error 11006 – Sign Mismatch Data Conversion

Why This Error Happens

Error 11006 occurs when SQL Server 2025 attempts to implicitly or explicitly convert a value between a signed and unsigned numeric data type (such as tinyint to smallint, or a negative value being forced into an unsigned column) and the conversion rules detect incompatible sign boundaries. This is typically triggered by linked server queries, CLR integration data type mapping, or poorly defined schema casts where a negative value cannot be represented in the target column’s unsigned range. It can also surface after an in-place upgrade to SQL Server 2025 if legacy stored procedures rely on deprecated implicit conversion behaviors that are now more strictly enforced.

Step-by-Step Resolution Guide

Step 1: Identify the Offending Query or Procedure

  • Check the SQL Server Error Log at C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG for the exact statement or batch ID tied to Error 11006.
  • Run SELECT * FROM sys.dm_exec_query_stats cross-referenced with sys.dm_exec_sql_text to pinpoint the exact T-SQL causing the cast failure.
  • Look specifically for CAST or CONVERT operations involving tinyint, smallint, int, or bigint mismatches.

Step 2: Correct the Data Type Definitions

  • Open SQL Server Management Studio (SSMS) 21 and navigate to the affected table via Object Explorer > Databases > [YourDB] > Tables.
  • Right-click the column in question and select Design, then explicitly change the data type to match the signed/unsigned expectation of the source system (e.g., change tinyint to smallint if negative values are expected).
  • Update any corresponding stored procedures or views using ALTER PROCEDURE to explicitly cast values using TRY_CONVERT instead of relying on implicit conversion.

Step 3: Patch and Validate SQL Server Configuration

  • Confirm SQL Server 2025 is running the latest Cumulative Update via SQL Server Configuration Manager or by running SELECT @@VERSION;.
  • If using Linked Servers, open Server Objects > Linked Servers > [ServerName] > Properties in SSMS and verify the Server Options for “Enable Promotion of Distributed Transactions” and data type mapping settings are consistent with the remote provider.
  • Restart the SQL Server service via services.msc or Restart-Service MSSQLSERVER in PowerShell (run as Administrator) to apply configuration changes.

Step 4: Rebuild Execution Plans

  • Clear the plan cache to remove any cached execution plans that may be enforcing stale type conversion metadata by running DBCC FREEPROCCACHE;.
  • Re-run the original query to confirm the cached plan is no longer forcing the invalid sign conversion.

Alternative or Verification Steps

  • Re-execute the originally failing query or application transaction and confirm no 11006 error appears in the Windows Event Viewer under Applications and Services Logs > MSSQLSERVER.
  • If the error persists, isolate the issue by wrapping the suspect column in TRY_CAST(column AS BIGINT) within a test query; a NULL result (instead of a hard failure) confirms the sign mismatch has been successfully bypassed and the schema/column fix below needs to be finalized.