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

by

Troubleshooting Guide: SQL Server Error 10659

Why This Error Happens

Error 10659 is actually an informational message, not a true failure condition — it is raised by SQL Server’s auditing/notification mechanism whenever an ALTER INDEX operation (such as REBUILD, REORGANIZE, DISABLE, or a column-store conversion) completes successfully on a given object. It typically surfaces in the SQL Server Error Log or Application Event Log because a DDL trigger, Extended Event, SQL Trace, or third-party monitoring tool is configured to capture and log schema-level changes for compliance or auditing purposes. Administrators often mistake it for an error because it appears alongside genuine error codes, but its presence usually indicates verbose logging, audit trails, or alerting rules are intercepting routine maintenance (index rebuild jobs, Maintenance Plans, or Ola Hallengren scripts) rather than an actual malfunction.

Step-by-Step Resolution Guide

Step 1: Confirm the Message is Informational, Not a Failure

  • Open SQL Server Management Studio (SSMS) and check SQL Server Logs under Management > SQL Server Logs.
  • Cross-reference the timestamp of Event ID 10659 with your index maintenance job (Agent Job history or Maintenance Plan logs) to confirm it aligns with a scheduled ALTER INDEX execution.
  • Verify there is no accompanying severity level 16+ error in the same log entry batch.

Step 2: Review Auditing and Extended Events Configuration

  • Navigate to SQL Server Management Studio > Management > Extended Events > Sessions and check if a session is capturing object_altered or audit_schema_object_management_event.
  • If using SQL Server Audit, run the following to list active audits:
SELECT * FROM sys.server_audits;
SELECT * FROM sys.server_audit_specifications;
  • Disable or scope down the audit specification if the logging volume is unnecessary for your compliance requirements.

Step 3: Check for DDL Triggers Generating the Message

  • Query for server- or database-level DDL triggers that may be printing or raising this message explicitly:
SELECT name, is_disabled FROM sys.triggers WHERE parent_class = 0;
SELECT name, is_disabled FROM sys.server_triggers;
  • If a custom trigger uses PRINT or RAISERROR referencing %S_MSG, review the trigger definition in sys.sql_modules and adjust its logging verbosity.

Step 4: Adjust Windows Event Log / SQL Server Log Verbosity

  • Open Event Viewer (eventvwr.msc) on Windows Server 2025 / Windows 11 and navigate to Applications and Services Logs > MSSQLSERVER.
  • If the volume of 10659 messages is flooding the log and causing performance or storage concerns, adjust the SQL Server error log retention via SSMS > Management > SQL Server Logs > Configure > Limit the number of error log files.
  • Restart the SQL Server service (services.msc → SQL Server (MSSQLSERVER) → Restart) only if log configuration changes require it.

Step 5: Validate Index Operation Completed Successfully

  • Run DBCC CHECKDB or check sys.dm_db_index_physical_stats to confirm the altered index is healthy and not fragmented or corrupted.
  • Review the Agent Job step history to confirm no actual errors (severity 16+) were thrown alongside the 10659 notice.

Alternative or Verification Steps

  • Verify the fix by re-running the index maintenance job manually and confirming that Event ID 10659 appears in the log only as an informational entry with no correlating error severity.
  • If the message volume remains disruptive, consider filtering it out at the monitoring/alerting tool level (e.g., SCOM, SolarWinds, or Redgate Monitor) by excluding Event ID 10659 from alert rules, since it does not indicate an actionable failure.