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

by

Troubleshooting Guide: SQL Server Error 1049 — Mixing Old and New Cursor Syntax

Why This Error Happens

This error occurs when a single DECLARE CURSOR statement combines the legacy Transact-SQL cursor syntax (e.g., INSENSITIVE, SCROLL before the cursor name) with the newer ISO/ANSI-compliant syntax (e.g., LOCAL, FAST_FORWARD, SCROLL_LOCKS after the CURSOR keyword) in the same query. SQL Server’s parser cannot reconcile both styles simultaneously because they represent two distinct grammar definitions for cursor declaration. This typically stems from copy-pasted legacy code being merged with newer T-SQL templates, or from migration scripts that were only partially updated during an upgrade to SQL Server 2025.

Step-by-Step Resolution Guide

Step 1: Identify the Offending Cursor Declaration

  • Open the stored procedure, function, or script referenced in the error message and locate the exact DECLARE CURSOR statement causing the failure.
  • Use SQL Server Management Studio (SSMS) 21 or Azure Data Studio to run the script in isolation and capture the precise line number from the error output.
  • Check for a mix of keywords such as INSENSITIVE, SCROLL (old syntax) alongside LOCAL, GLOBAL, FORWARD_ONLY, STATIC, KEYSET, DYNAMIC, FAST_FORWARD, READ_ONLY, SCROLL_LOCKS, or OPTIMISTIC (new syntax) in the same declaration.

Step 2: Rewrite the Cursor Using a Single Syntax Standard

  • Choose either the old-style syntax: DECLARE cursor_name [INSENSITIVE] [SCROLL] CURSOR FOR select_statement.
  • Or the new-style (ISO) syntax: DECLARE cursor_name CURSOR [LOCAL | GLOBAL] [FORWARD_ONLY | SCROLL] [STATIC | KEYSET | DYNAMIC | FAST_FORWARD] [READ_ONLY | SCROLL_LOCKS | OPTIMISTIC] FOR select_statement.
  • Update the script so all cursor option keywords belong to only one of these two patterns—do not blend keywords from both lists.

Step 3: Validate Syntax Using SQL Server 2025 Compatibility Tools

  • Run the updated script against a compatibility level 170 database using sp_dbcmptlevel to confirm the new syntax parses correctly.
  • Use the Database Engine Tuning Advisor or SET PARSEONLY ON in SSMS to perform a dry-run syntax check without executing the full batch.
  • Search the codebase (via sys.sql_modules or source control) for other instances of the same anti-pattern, especially in migrated procedures from SQL Server 2014 or earlier.

Step 4: Deploy and Test the Corrected Script

  • Save the corrected stored procedure or script and redeploy it to the target database on Windows Server 2025.
  • Execute the procedure manually with test parameters to confirm Error 1049 no longer appears in the SSMS Messages tab or the SQL Server error log (Logs folder under the instance’s MSSQL directory).

Alternative or Verification Steps

  • Verify the fix by re-running the script and confirming successful execution with zero syntax errors; also check SQL Server Logs via SSMS Object Explorer > Management > SQL Server Logs for any recurrence of Error 1049.
  • As an alternative, use SQL Server’s built-in Database Compatibility Level Upgrade Advisor to batch-scan all stored procedures for deprecated or mixed cursor syntax before manually rewriting each one.