Zabbix: Mssql Failed To Fetch Info Data -or No Data For 30m- __full__

The monitoring database user requires specific privileges. Without VIEW SERVER STATE permission, the user cannot access the dynamic management views (DMVs) that provide performance counters and instance information.

Modern Zabbix MSSQL templates rely on DMVs ( sys.dm_os_performance_counters , sys.dm_exec_requests , etc.). Without VIEW SERVER STATE , DMVs return empty result sets – no error, just no data.

The Network Operations Center hummed its usual lullaby of cooling fans and low conversation. On the wall, a massive screen displayed a constellation of green dots—each one a server, a service, a heartbeat. In the center of that constellation, glowing a steady, reassuring emerald, was .

The cause of this "no data" scenario is almost never a single, obvious problem. It is typically the result of a breakdown somewhere in the complex chain of connections that spans from the Zabbix server all the way to the SQL Server's internal performance counters. This guide provides a systematic, step-by-step approach to diagnose and resolve the issue.

MSSQL instances with hundreds of databases or heavy transactional loads can experience delays when processing Zabbix discovery rules. If the query takes longer than the Zabbix agent or proxy timeout limit, it returns no data. zabbix mssql failed to fetch info data -or no data for 30m-

Zabbix’s ODBC DSN often uses Server=localhost\INSTANCE . This requires SQL Browser (UDP port 1434) to resolve the dynamic port. If SQL Browser is disabled, the connection hangs then fails.

Plugins.MSSQL.Timeout=30

mssql.custom.query[Server=.;Trusted_Connection=True;,SELECT cntr_value FROM sys.dm_os_performance_counters WHERE object_name='SQLServer:Buffer Manager' AND counter_name='Buffer cache hit ratio']

To streamline your efforts, follow this checklist in order: The monitoring database user requires specific privileges

MSSQL: Failed to fetch info data (or no data for 30m) - Zabbix

Go to and filter by your host. Look for the master item (often named MSSQL: Get performance counters or similar). Click Check now . Review the returned value. If it is an error message or empty, use that text to pinpoint the cause.

The monitoring user must have specific rights to query system views like sys.dm_os_performance_counters . Without VIEW SERVER STATE (or VIEW SERVER PERFORMANCE STATE for SQL 2022+), the "Get Info" queries return empty results.

She clicked on the item: MSSQL: User activity per minute . Without VIEW SERVER STATE , DMVs return empty

<!-- Item to track fetch failures --> <item name="MSSQL: Info fetch status" key="mssql.info.fetch.status"> <type>Zabbix agent</type> <key>perf.ms sql[fetch.status]</key> <value_type>Numeric (unsigned)</value_type> <units>status</units> <delay>60s</delay> <description>1 = fetch failed, 0 = fetch successful</description> </item>

odbcinst -q -d

The "MSSQL: Failed to fetch info data (or no data for 30m)" error is usually not a bug but a symptom of a missing dependency, misconfiguration, or permission issue. By systematically verifying the ODBC layer, the SQL Server permissions, the Zabbix macros, and the timeout settings, you can quickly restore full monitoring functionality. Regular testing using manual tools like isql and reviewing the Zabbix logs are the most effective ways to diagnose and prevent this error from recurring.

She bypassed Zabbix entirely. She logged into the SQL server via an emergency admin account and issued the kill command for the orphaned Zabbix query. Then, with shaking fingers, she typed: