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

by

Troubleshooting Guide: SQL Server Error 279 – “Getting Data” Text Error

Why This Error Happens

Error 279 in Microsoft SQL Server 2025 typically occurs when the ntext, text, or image data types are referenced in an operation that no longer supports them, as these types are deprecated in favor of nvarchar(max), varchar(max), and varbinary(max). This error can also surface when a corrupted result set metadata cache prevents the client application from correctly rendering the “Getting Data” placeholder text in SQL Server Management Studio (SSMS) or Azure Data Studio. Additionally, permission misalignments on Windows Server 2025 related to the SQL Server service account can interrupt the data retrieval stream, causing the client to hang on this message indefinitely.

Step-by-Step Resolution Guide

Step 1: Verify Deprecated Data Type Usage

  • Open SQL Server Management Studio (SSMS) and connect to the target instance.
  • Run the following query to check for legacy data types in your schema:
  SELECT t.name, c.name AS ColumnName, o.name AS TableName
  FROM sys.columns c
  JOIN sys.types t ON c.user_type_id = t.user_type_id
  JOIN sys.objects o ON c.object_id = o.object_id
  WHERE t.name IN ('text', 'ntext', 'image');
  • If results are returned, plan to migrate these columns to MAX data types using an ALTER TABLE statement.

Step 2: Clear the Client-Side Cache and Temp Files

  • Close SSMS or Azure Data Studio completely.
  • Navigate to %AppData%\Local\Microsoft\SQL Server Management Studio\ and delete the cache folder for your specific version (e.g., 18.0 or 20.0).
  • Restart the application and attempt to reconnect to the Windows Server 2025 instance to force a fresh metadata pull.

Step 3: Reset Service Account Permissions

  • Open the Services application (services.msc) on Windows Server 2025.
  • Locate SQL Server (MSSQLSERVER) or your named instance.
  • Right-click, select Properties, and navigate to the Log On tab to ensure the service account has “Log on as a service” rights via the Local Security Policy (secpol.msc).
  • Restart the SQL Server service to apply the permission changes.

Step 4: Rebuild the Resource Database

  • If the error persists, verify the integrity of the mssqlsystemresource.mdf file located in the Binn\Template Data folder of your SQL Server 2025 installation directory.
  • Use the SQL Server 2025 setup wizard’s Repair feature to rebuild the resource database without affecting user data.

Alternative or Verification Steps

  • Verification: Run a simple SELECT TOP 10 * FROM [YourTable] on a table that previously threw the error; if data populates instantly instead of hanging on “Getting Data,” the fix was successful.
  • Alternative: If the error remains, try connecting via sqlcmd in Command Prompt on Windows 11 to bypass the SSMS GUI rendering engine entirely and confirm if the issue is client-side or server-side.