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

by

Why This Error Happens

Error 3614 is not a true failure condition—it is an informational diagnostic message that SQL Server writes to the error log when internal verbose logging trace flags (such as 3004, 3213, or 3605) are enabled, typically for backup/restore or checkpoint performance tuning. The “Batch Statistics: Overall Duration” output is generated by the Storage Engine’s internal timing instrumentation, which gets triggered when these trace flags are active globally or at the session level. Because it is logged with a message ID, monitoring tools or log parsers often misclassify it as a critical error, when in reality it simply reports batch execution timing.

Step-by-Step Resolution Guide

Step 1: Identify Active Trace Flags

  • Connect to the instance via SSMS or sqlcmd and run DBCC TRACESTATUS(-1); to list all currently enabled trace flags.
  • Look specifically for 3004, 3213, 3605, or 1204/1222 (locking diagnostics), as these commonly trigger verbose batch statistics logging.
  • Check the SQL Server startup parameters in SQL Server Configuration Manager > SQL Server Services > Properties > Startup Parameters for any -T flags that persist across restarts.

Step 2: Disable Unnecessary Verbose Logging

  • If the trace flags were enabled for a one-time diagnostic session, turn them off immediately using DBCC TRACEOFF (3004, 3213, -1);
  • If they were set at the service level via startup parameters, remove the corresponding -T3004 or -T3213 entries in Configuration Manager.
  • Restart the SQL Server service for the startup parameter changes to take effect: Restart-Service -Name 'MSSQLSERVER' (PowerShell, run as Administrator on Windows Server 2025).

Step 3: Adjust Error Log Verbosity and Filtering

  • Open SQL Server Management Studio > Management > SQL Server Logs and confirm whether the batch statistics messages continue after trace flags are disabled.
  • If you need to retain some diagnostic flags for ongoing backup compression tuning, redirect this noise by filtering Event Viewer/Log Viewer queries to exclude Message ID 3614 using the SSMS log filter dialog (Log Entry contains field, set to exclude “Batch Statistics”).
  • Ensure the SQL Server Error Log path (default: C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) isn’t growing excessively due to this verbose output; cycle the log via EXEC sp_cycle_errorlog; if needed.

Step 4: Validate Application and Job Dependencies

  • Check SQL Server Agent jobs, maintenance plans, or third-party backup tools (e.g., for full/differential backups) that may explicitly enable these trace flags via WITH TRACEFLAG hints in backup scripts.
  • Remove or comment out any DBCC TRACEON calls embedded in T-SQL job steps that are no longer required for troubleshooting.

Alternative or Verification Steps

  • Re-run DBCC TRACESTATUS(-1); after remediation to confirm no unwanted trace flags remain active, and monitor the ERRORLOG for a few hours to verify Error 3614 no longer appears.
  • If verbose statistics are still required for ongoing performance analysis, redirect output to Extended Events sessions instead of the main error log, using CREATE EVENT SESSION with a ring_buffer or file target to isolate diagnostic noise from production logs.