If the SQL service is running, the issue might be between the Zabbix Server and the Agent on the SQL host.

On the Zabbix Server, run:

zabbix_get -s <TARGET_IP> -k agent.ping

The "No data for 30m" error in MSSQL monitoring is rarely a network outage and almost always a script execution failure. By increasing the Timeout parameter to accommodate heavy SQL queries and ensuring PowerShell Execution Policies allow the scripts to run, administrators can restore data flow and maintain visibility into their database infrastructure.

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”.

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.

| Cause | Solution | |-------|----------| | Permission denied | GRANT VIEW SERVER STATE TO zabbix_user; | | Missing database | Ensure referenced DB is online or use WHERE DB_NAME() = 'master' | | SQL syntax error | Test query in SSMS before putting in Zabbix item. | | Agent 2 misconfiguration | Use correct connection string: Server=.;Trusted_Connection=True; |