These permissions are the minimum required for the official "MSSQL by ODBC" template to function correctly.
nodata(/YourHost/perf_instance["SQLServer:Databases(_Total)\Data File(s) Size (KB)",_Total],30m)=1 and last(/YourHost/perf_instance[...])<>0
From the Zabbix server CLI:
The (shipped with Zabbix 6.0+) is robust when properly configured. zabbix mssql failed to fetch info data -or no data for 30m-
This is often the root cause. Zabbix cannot establish a connection to the MS SQL Server at all. Symptoms may include a complete absence of data for all items related to the template, errors in Zabbix logs indicating a failed connection, or a ZBX_NOTSUPPORTED status for items like mssql.ping . A common manifestation is the Data source name not found error, indicating that the DSN (Data Source Name) configured in Zabbix is not recognized by the system.
Note: If using the MSSQL plugin directly, you can also look for Plugins.MSSQL.Timeout=15 inside the configuration file. For Zabbix Server or Proxy:
telnet <MSSQL_server_IP> 1433
The Zabbix alert is a common and frustrating issue that database administrators and DevOps engineers encounter when setting up Microsoft SQL Server monitoring.
From your Zabbix server, run: telnet
When installing Zabbix Agent 2, the installer creates a dedicated configuration file for SQL Server called mssql.conf . By default, this file is often nested within an inactive subdirectory where Agent 2 ignores it. These permissions are the minimum required for the
The monitoring user needs very specific permissions to query the correct performance data. Using the "sa" account is not recommended. Follow the official guidance and grant the following permissions on your SQL Server:
Replace the variables with your actual values. If this fails, Zabbix will not work either.
: If using a named instance, ensure the macro $MSSQL.INSTANCE is set correctly (e.g., MSSQL$InstanceName ). For default instances, this macro should remain unchanged. Zabbix cannot establish a connection to the MS
You’ll see SQLServer:Puffermanager instead of SQLServer:Buffer Manager .