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

"MSSQL: Failed to fetch info data (or no data for 30m)" typically indicates a failure in the communication link between the Zabbix Agent (or Server) and the SQL Server instance

. This is most often caused by incorrect credentials, missing ODBC drivers, or misconfigured connection parameters. Common Causes and Solutions Missing or Misconfigured ODBC Driver

: If you are using the "MSSQL by ODBC" template, ensure the Microsoft ODBC Driver is installed on the Zabbix Server (for passive checks) or Proxy. Verify that the driver is correctly defined in /etc/odbcinst.ini Authentication Issues

: The Zabbix monitoring user must have specific permissions to access system views. Ensure the user has VIEW SERVER STATE VIEW SERVER PERFORMANCE STATE for MSSQL 2022) and VIEW ANY DEFINITION permissions.

Verify that the credentials in your Zabbix host macros (e.g., $MSSQL.USER $MSSQL.PASSWORD ) match the SQL login. Connection String Problems Port Syntax : Microsoft SQL Server does not use the directive in some ODBC configurations; use Server = ipaddress,1433 (comma instead of colon). Encryption & Certificates zabbix mssql failed to fetch info data -or no data for 30m-

: If the SQL Server requires encrypted connections, you may need to add Encrypt=yes to the connection string or TrustServerCertificate=yes if you are using self-signed certificates. Agent 2 Plugin Configuration

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

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

from the command line on the Zabbix server/agent host to verify that the connection works outside of Zabbix. Check Zabbix Logs : Look at the Zabbix Server or Agent log files (usually in /var/log/zabbix/ "MSSQL: Failed to fetch info data (or no

) for more specific error details, such as "Login failed" or "Driver not found". Increase Timeout

: If the SQL instance is under heavy load, the info fetch might timeout. Try increasing the parameter in the Zabbix server/agent configuration files. Detect Issues in Your Zabbix Instance Before It's Too Late 25 Mar 2026 —

Case 2: The Azure SQL Managed Instance

Symptom: “Failed to fetch info data” immediately.

Root cause: Azure SQL Managed Instance does not support sys.dm_os_performance_counters – it raises “Invalid object name”. Case 2: The Azure SQL Managed Instance Symptom:

Solution: Switch to sys.dm_db_resource_stats or sys.server_resource_stats views. Customize the user parameter to query these instead. The official Zabbix template for Azure SQL Database is different from on-prem MSSQL.

Step 1: Verify Zabbix Configuration

  1. Check the Zabbix configuration file (zabbix_server.conf or zabbix_agentd.conf) for any errors or typos.
  2. Ensure that the MSSQL monitoring template is correctly configured and linked to the host.
  3. Verify that the host and item configurations are correct.

Zabbix Trigger Expression

Your_Template:mssql.info.fetch.fail.min(30m)=1 or Your_Template:mssql.info.fetch.data.nodata(30m)=1

Fix D: Optimize Zabbix Agent Performance for Many SQL Items

If you monitor dozens of SQL Server instances per agent, the default polling may collapse.

Apply these in zabbix_agentd.conf:

StartAgents=32
Timeout=30
ODBCPoolSize=100
EnableRemoteCommands=1

Restart the agent. Also, spread items across multiple trapper items or use a Zabbix proxy for distributed SQL monitoring.

Part 4: Fixing the Problem – Permanent Solutions

Step 3: Investigate MSSQL Server Configuration

  1. Check the MSSQL server configuration and ensure that it's running and accepting connections.
  2. Verify that the database and login credentials used by Zabbix have the necessary permissions.
  3. Check the SQL Server error log for any issues or errors related to the Zabbix connection.

3.3 Timeout & Resource Constraints (No data for 30m)

  • ODBC timeout – Default QueryTimeout (e.g., 5s) too short for heavy DMVs.
  • Zabbix server poller timeout – Timeout=3 in zabbix_server.conf insufficient for slow queries.
  • MSSQL resource governor throttling Zabbix login.

Step 4: Analyze Monitoring Item Configuration

  1. Review the monitoring item configuration in Zabbix and ensure that it's set up correctly.
  2. Verify that the query syntax is correct and the database connection is properly configured.
  3. Check the monitoring item's history and trends to see if there are any issues with data collection.
zabbix mssql failed to fetch info data -or no data for 30m-