Mssql: Failed To Fetch Info Data (or No Data For 30m) -

If the SQL Server looks healthy, the issue may be with the monitoring agent itself.

Host macros such as $MSSQL.USER , $MSSQL.PASSWORD , and $MSSQL.URI may have incorrect values or be missing. mssql: failed to fetch info data (or no data for 30m)

If SQL counters are missing, you may need to reload them using the lodctr /R command in an elevated prompt. 4. Troubleshoot ODBC & Drivers If you are using an ODBC-based template: If the SQL Server looks healthy, the issue

To resolve the "Failed to fetch" alert, follow these systematic checks: 1. Verify Connectivity | | Query Performance | Blocking queries, deadlocks,

| Category | Specific Cause | |----------|----------------| | | Network firewall dropping long‑living connections; DNS resolution issues; Azure SQL Gateway timeout. | | Query Performance | Blocking queries, deadlocks, or an inefficient sys.dm_os_performance_counters query that exceeds 30 min. | | Resource Exhaustion | TempDB full, transaction log full, or memory pressure stalling system DMV responses. | | Monitoring Agent Behavior | Hardcoded 30‑min socket timeout; missing retry logic; synchronous fetch from a busy sys.dm_exec_requests . | | SQL Server Configuration | remote query timeout set to 0 (unlimited) causing indefinite wait; query wait high. | | External Dependencies | Anti‑virus scanning .mdf/.ldf files; backup job holding shared locks on system tables. |

GRANT VIEW SERVER STATE TO [User] (or VIEW SERVER PERFORMANCE STATE for MSSQL 2022+).

Firewalls or network security groups may be blocking the connection on port 1433 or other custom ports.