Each UserParameter that runs a T-SQL query (like db.mssql.get from the official template) opens a new ODBC connection. If you have 5 databases × 30 items, the agent may exceed its Timeout setting (default 3 seconds) or ODBC connection pool limit.
If manual fails, the issue is OS/ODBC layer.
file on the target host. Restart the Zabbix Agent 2 service after making any changes. Macro URI Errors : Ensure the $MSSQL.URI macro is correctly formatted as sqlserver:// : or uses a named session defined in the agent configuration. Troubleshooting Steps Test Connection Manually (for ODBC) or zabbix mssql failed to fetch info data -or no data for 30m-
ybcnyc. Junior Member. Joined: Jun 2022. Posts: 1. MSSQL monitoring - MSSQL: Failed to fetch info data (or no data for 30m) 16-06-
SELECT DISTINCT object_name FROM sys.dm_os_performance_counters; Each UserParameter that runs a T-SQL query (like db
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
Update your connection string or the host's $MSSQL.ODBC.STR macro to explicitly trust the target database certificate: file on the target host
On the host macro level, set:
Because the underlying master items rely on either or the Zabbix Agent 2 MSSQL plugin , a failure at this root level cascades across your entire monitoring tree, resulting in blank dashboards, broken triggers, and lack of visibility into your database infrastructure. Root Causes of the MSSQL Fetch Failure