By default, Zabbix components have a strict 3-second timeout for executing scripts and queries. On large, highly transactional, or heavily loaded MSSQL instances, gathering system information can take longer than 3 seconds, causing Zabbix to drop the connection and report "no data." You must increase this limit in your configuration files. For Zabbix Agent 2:
SQL Server is running, but network protocols prevent remote connections. zabbix mssql failed to fetch info data -or no data for 30m-
