!link! | Zabbix Mssql Failed To Fetch Info Data -or No Data For 30m-

A service restart can clear hung connections. systemctl restart zabbix-agent2 Use code with caution.

Run the following SQL script to grant the necessary permissions to the Zabbix monitoring user (adjust for your MSSQL version):

: If using "MSSQL by Zabbix agent 2", the plugin configuration must be present in the zabbix_agent2.d/mssql.conf

-- Grant server-level permissions GRANT VIEW SERVER STATE TO zbx_monitor; GRANT VIEW ANY DEFINITION TO zbx_monitor; -- Grant both for comprehensive monitoring

The isql test uses your system's environment. To truly test what the Zabbix server sees, use the zabbix_get command. This command simulates a Zabbix poller request. zabbix mssql failed to fetch info data -or no data for 30m-

On the host macro level, set:

The error message appears when:

You need to grant the Zabbix Agent user access to the SQL Server instance.

or Zabbix macros, the port must be specified after a comma, not a colon (e.g., Server = 192.168.1.50,1433 as a separate directive often fails. Macro Configuration : Verify that your host macros are correctly set: $MSSQL.USER $MSSQL.PASSWORD $MSSQL.DSN (must match the name in your /etc/odbc.ini on the Zabbix server/proxy). Agent 2 Configuration A service restart can clear hung connections

She watched the clock tick over to .

Look for the $MSSQL.TIMEOUT macro in your Zabbix host configurations and increase it to 15 or 20 seconds.

When the Zabbix MSSQL by ODBC or MSSQL by Zabbix agent template is used, Zabbix expects regular check-ins (e.g., every 5 minutes). If the server returns empty data, crashes, or times out, the nodata() function in Zabbix triggers this alert after 30 minutes of silence. Incorrect ODBC credentials or permissions.

If you continue to face issues after these steps, it is recommended to review the in the frontend to get specific error codes regarding the failed to fetch message. To truly test what the Zabbix server sees,

: The DSN name in your Zabbix macro $MSSQL.DSN must exactly match the header in your odbc.ini file.

This piece will trigger when:

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.