Templates available in Database Servers category
The below templates are predefined to monitor database services and appliances. Learn more about templates.
The below templates belong to Database Servers category:
Microsoft SQL Database Server is a relational database management system (RDBMS) developer by Microsoft. SQL Server version 9.0 (named SQL Server 2005) and above are supported.
Microsoft SQL Express Database Server, a free version of commercial MS SQL software, with artificial hardware restrictions and other limitations (such as maximal database size).
MySQL 5.7.X Database Server, latest version of MySQL 5.X RDBMS (owned currently by Oracle), currently one of most popular free RDBMS product.
MySQL 5.[1-6].X Database Server, older (including legacy) versions of MySQL 5.X product, still widely in use.
Oracle Database Server, one of most popular RDBMS supplied by Oacle Corporation; it also is available in free (“Express”) edition, DB XE, with limitation on database size, features available and hardware used.
Oracle Database Server on Windows Host is same as above, but installed on Windows host (with corresponding OS specifics).
Database Server monitoring use cases
- unless it is discovery, when database servers’ actual version and capacity are detected using automated tests, type and version of database server is usually known; try to match the monitor as close a possible: e.g., use Oracle Database Server or Oracle Database Server on Windows Host, depending on the platform DBMS is using
- when monitoring MySQL forks (including those marked as drop-in replacements – Drizzle, MariaDB, Percona server etc) use corresponding MySQL template, i.e. MySQL 5.7.X Database Server or MySQL 5.[1-6].X Database Server; not that it’s not always possible to match exactly the same features even if the fork claims full compatibility
Database Servers monitoring tips
- always use secure connection to DBMS server; the only exception is connecting to 127/8 (localhost) addresses, which are considered safe without using encryption
- for general database health checks, create a separate database, perhaps with single table, create users credentials for it if applicable, and run queries only against that table – for security reasons
- never utilize DBMS credentials used by any production application, create a separate credentials set instead
- assign as little permissions to DBMS credentials as possible
- when applicable, use well-known optimization checking scripts, like MySQLTuner, to detect DB problems and report them from monitors