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

by

Troubleshooting Guide: SQL Server Error 4074 – Result Set Column Limit Exceeded

Why This Error Happens

Error 4074 occurs when a query attempts to return a result set containing more than 65,535 columns, which exceeds the hard limit imposed by the TDS (Tabular Data Stream) protocol that client drivers use to communicate with SQL Server. This typically happens with dynamically generated queries, wide PIVOT operations, or applications that programmatically concatenate large numbers of columns via SELECT * across multiple joined tables. It is not caused by corruption or permissions — it is a protocol-level restriction that client libraries (ODBC, OLE DB, JDBC) enforce and cannot bypass.

Step-by-Step Resolution Guide

Step 1: Identify the Offending Query

  • Capture the exact query using SQL Server Profiler, Extended Events, or the application’s query log.
  • Check the SELECT statement for wildcard usage (SELECT *) across multiple joined or pivoted tables.
  • Confirm the column count by running the query in SSMS and checking the “Results” pane column header count, or use sys.dm_exec_describe_first_result_set.

Step 2: Reduce the Returned Column Count

  • Rewrite the query to explicitly select only required columns instead of using SELECT *.
  • If using PIVOT, limit the number of distinct values being pivoted into columns (consider pivoting in batches).
  • For dynamic SQL generation (common in reporting tools), add a validation check in the stored procedure to cap column count before execution:
  • IF (SELECT COUNT(*) FROM sys.dm_exec_describe_first_result_set(@sql, NULL, 0)) > 65535 RAISERROR(...)

Step 3: Refactor Schema or Application Logic

  • If the underlying table design relies on wide tables (e.g., sparse columns, EAV patterns), consider normalizing the schema into multiple narrower tables.
  • Replace extremely wide JOIN chains with separate queries executed individually and merged at the application layer instead of within SQL Server.
  • For reporting/BI tools (SSRS, Power BI, Excel), paginate column output or use row-based transposition instead of column-based transposition.

Step 4: Update Client Drivers and Connection Settings

  • Ensure you are using the latest ODBC Driver (18+) or OLE DB Driver (MSOLEDBSQL) compatible with SQL Server 2025 on Windows Server 2025 / Windows 11.
  • Check driver installation path: C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\{version}\
  • Reinstall or repair the driver via Settings > Apps > Installed Apps on Windows 11, or Programs and Features on Windows Server 2025, if corruption is suspected.

Alternative or Verification Steps

  • Re-run the original query after modification and confirm successful execution without Error 4074 in SSMS or the application log.
  • As a temporary workaround, split the result set into multiple smaller queries (each under 65,535 columns) and reassemble the data client-side using application code (e.g., C# DataTable merge or Python pandas concat).