PiotrJ. Junior Member. Joined: May 2023. Posts: 26. Problem: MSSQL: Failed to fetch info data (or no data for 30m) 21-09-2023, 19:
Define a session name (e.g., SQLServer1 ) and its connection details:
The (shipped with Zabbix 6.0+) is robust when properly configured. zabbix mssql failed to fetch info data -or no data for 30m-
The Zabbix monitoring user requires specific permissions to access system views and performance counters. If these are missing, the query that fetches "info data" will fail. Ensure the monitoring user has these permissions: SERVER STATE [zabbix_user]; DEFINITION [zabbix_user]; -- For SQL Agent jobs monitoring: dbo.sysjobs [zabbix_user]; dbo.sysjobactivity [zabbix_user]; dbo.agent_datetime [zabbix_user]; Use code with caution. Copied to clipboard 2. ODBC Driver Configuration (Zabbix Server/Proxy)
timeout 10 $MSSQL_CMD -S $SERVER -d $DB -Q "$QUERY" -W -h -1 > /dev/null 2>&1 PiotrJ
First, it's crucial to understand what this error message means. It is not a single error but a consequence of other, more specific failures. The trigger expression itself is nodata(/MSSQL by ODBC/mssql.uptime,30m)=1 . In plain English, this means the Zabbix server is checking the mssql.uptime item. If it hasn't received a new value for that item in 30 minutes, it fires this alarm.
Update your connection string or the host's $MSSQL.ODBC.STR macro to explicitly trust the target database certificate: Posts: 26
Encountering the "failed to fetch info data (or no data for 30m)" error can be frustrating, but it is highly diagnostic. It is almost always caused by one of the fundamental components in the data chain: connectivity, permissions, configuration, or a known software bug.
Your database is still running. Queries are working. But Zabbix has gone blind. In the world of infrastructure monitoring, no data is often more dangerous than bad data . It creates false confidence, hides disk space exhaustion, and masks deadlocks until users start screaming.
Before you do anything in Zabbix, test the connection from the command line. This bypasses Zabbix entirely and isolates driver issues.
: In some template versions, check the "Get Buffer Manager counters" item. If it shows "Not Supported," verify that the JSON path in the item's preprocessing is correct for your SQL version.
