PostgreSQL Monitoring Categories
| Category | Description | Actions Available |
|---|---|---|
| [PostgreSQL SQL Statements][] | Execute custom SQL queries against PostgreSQL instances; monitor business data and validate health checks | [Execute Script][] · Edit Query · View Results History |
Detailed Actions by Category
Using the self-service enabled [Web Client][] for Nodinite, [Remote Actions][] can be sent by the Database Monitoring Agent to perform operations on monitored [Resources][]—without SSMS, Azure portal, or elevated privileges. With the existing privilege model, you can allow certain users to perform operations on hand-picked resources.
SQL Server Actions:
[SQL Backups][] – Edit Thresholds
[SQL Blocking][] – Details · Kill Blocking Session
[SQL Instance][] – View SQL Log (Current) · Details
[SQL Jobs][] – View Job History · Edit Thresholds · Start Job · Start Job at Step · Stop Job · Enable Job · Disable Job
[SQL Size Checks][] – Edit Size Thresholds (Data and Log separately)
[SQL SSIS][] – View SSIS Run History (individual packages/projects)
[SQL Statements][] – Edit SQL Statements · [Execute Script][] (Stored Procedures and AdHoc TSQL)
Azure SQL Database Actions:
[Azure Size Checks][] – Edit Size Thresholds
[Azure SQL Statements][] – Edit SQL Statements · [Execute Script][] (Stored Procedures and AdHoc TSQL)
PostgreSQL Actions:
[PostgreSQL SQL Statements][] – Edit SQL Statements · [Execute Script][] (AdHoc SQL)
Supported Database Versions
| Product | Supported Versions | Comment |
|---|---|---|
| SQL Server | 2008 R2, 2012, 2014, 2016, 2017, 2019 (version history) | All editions supported: Preview, Developer, Standard, Enterprise. Default and named instances both supported. |
| SQL Express | 2008 R2, 2012, 2014, 2016, 2017 (version history) | Not all monitoring features available due to SQL Server Express limitations (e.g., no SQL Agent, limited SSIS support). |
| Azure SQL Database | All current Azure SQL Database tiers | Not all monitoring features available due to Azure SQL Database platform limitations (e.g., no SQL Agent, no SSISDB catalog). |
| PostgreSQL | v9 and later (versioning) | Earlier versions may work—contact Nodinite Support for compatibility with older PostgreSQL versions. |
Note
Our aim is always to support the latest database versions and standards, often including CTP (Community Technology Preview) releases as we develop on the latest technologies. Contact Nodinite Support for specific version compatibility questions.
Get Started
| Step | Task | Description |
|---|---|---|
| 1 | [Review Prerequisites][Prerequisites for Database Monitoring Agent] | Confirm SQL Server/Azure SQL/PostgreSQL credentials, network connectivity, and required permissions (db_datareader for backups, VIEW SERVER STATE for blocking, SQLAgentOperatorRole for jobs). |
| 2 | [Install the Agent][Install Database Monitoring Agent] | Download the Database Monitoring Agent installer, run on Windows Server with IIS, configure database connection strings, and register the agent with Nodinite Core Services. |
| 3 | [Configure Monitoring Resources][Configuration] | Add SQL Server instances, Azure SQL databases, and PostgreSQL connections as [Resources][]; configure categories (Backups, Jobs, Blocking, SSIS, Size Checks, SQL Statements) based on monitoring needs. |
| 4 | Set Up Alerts | Define alert thresholds (backup overdue >24 hours, blocking >5 minutes, job failure, disk space <20% free); configure notification channels (email, Teams, ticketing systems). |
| 5 | Create Dashboards | Build custom dashboards in Nodinite [Web Client][] showing backup status, job success rates, space utilization trends, blocking frequency—tailored for DBAs, operations, and business users. |
| 6 | Delegate Access | Use role-based access to grant operations teams permission to view [Monitor Views][], start/stop jobs, execute scripts—without granting sysadmin or Azure contributor roles. |
Common Questions
Q: Can I monitor multiple SQL Server instances from one Database Monitoring Agent?
A: Yes. A single Database Monitoring Agent can monitor an unlimited number of SQL Server instances, Azure SQL databases, and PostgreSQL instances. You can deploy multiple agents for geographic distribution, network segmentation, or workload isolation.
Q: What permissions are required to monitor SQL Server?
A: Minimum permissions vary by category: Backups require db_datareader on msdb (to read backup history), Blocking requires VIEW SERVER STATE, Jobs require membership in SQLAgentOperatorRole or SQLAgentUserRole, SSIS requires ssis_admin role on SSISDB catalog. For least-privilege setup, see [Prerequisites for Database Monitoring Agent][].
Q: Can I execute remote actions without granting sysadmin rights?
A: Yes. Using SQL Server role-based security and Nodinite's privilege model, you can delegate specific actions (start/stop jobs, execute predefined scripts, kill blocking sessions) to operations teams without granting sysadmin. The agent uses service accounts with targeted permissions for each action type.
Q: What are the limitations when monitoring Azure SQL Database vs. SQL Server?
A: Azure SQL Database does not include SQL Server Agent (no job monitoring), SSISDB catalog (no SSIS monitoring), or some DMVs (limited blocking details). You can monitor Azure SQL Database size checks, custom TSQL statements, and execute scripts. For job-like scheduling in Azure, consider Azure Data Factory and use the Nodinite [Web Services Agent][] to monitor Data Factory pipelines.
Q: Can I monitor SQL Express with this agent?
A: Yes, but SQL Server Express has platform limitations: no SQL Server Agent (no job monitoring), limited SSIS support (no SSISDB catalog). You can monitor SQL Express backups, blocking, instance health, size checks, and custom TSQL statements.
Q: How do I monitor custom business logic or data quality with TSQL queries?
A: Use the [SQL Statements][] category to add custom TSQL queries. The agent executes your SELECT statement on a schedule, evaluates the result (row count, column values), and triggers alerts based on thresholds you configure. Example: SELECT COUNT(*) FROM Orders WHERE Status='Pending' AND OrderDate < DATEADD(day,-1,GETDATE())—alert if result >10.
Q: Can I monitor PostgreSQL alongside SQL Server from the same agent?
A: Yes. The Database Monitoring Agent supports SQL Server, Azure SQL Database, and PostgreSQL from the same installation. Add PostgreSQL instances as [Resources][] and configure [PostgreSQL SQL Statements][] to execute custom health checks and monitor query results.
Q: How do alerts work when backups fail or jobs fail?
A: The agent monitors backup history and job execution on a schedule (configurable interval, typically every 5-15 minutes). When a backup exceeds your configured threshold (e.g., "no full backup in 24 hours") or a job fails, the agent updates the resource state to "Error" in [Monitor Views][], triggers configured [Alerts][] (email, Teams, ticketing), and logs the event. You can view historical trends in [Reports][] or dashboards.
Q: What happens if the Database Monitoring Agent host server loses connectivity to a SQL Server?
A: The agent will detect connectivity failure during the next monitoring cycle, mark the SQL Server instance resource as "Error" with a connectivity failure message, and trigger alerts. Once connectivity is restored, the agent resumes normal monitoring automatically—no manual intervention required.
Additional Resources
- Release Notes – Review the latest features, bug fixes, and version history for the Database Monitoring Agent
- [Troubleshooting Database Monitoring Agent][Troubleshooting] – Diagnose common issues: connectivity, permissions, performance, alert configuration
- [Updating Database Monitoring Agent][Updating] – Learn how to upgrade the agent to the latest version with minimal downtime
- [Prerequisites for Database Monitoring Agent][Prerequisites for Database Monitoring Agent] – Detailed credential, permission, and network connectivity requirements
- [Features Overview][SQL Categories] – Explore all monitoring categories and capabilities in depth
- [Monitor Views][] – Learn how to use Monitor Views to visualize database health and investigate issues
- [Remote Actions][] – Complete reference for remote actions available per category
- [Reports][] – Design custom reports for backup compliance, job success rates, space trends, and more
- [Repository Model][] – Document your databases with metadata, ownership, SLAs, and dependencies
Next Step
Ready to start monitoring? Install the Database Monitoring Agent and configure your first SQL Server or Azure SQL Database:
[Install Database Monitoring Agent][] – Download and install the agent on Windows Server with IIS
[Configuration][] – Add SQL Server instances, Azure SQL databases, or PostgreSQL as monitored resources
Related Database Monitoring Solutions
- [BizTalk Agent][] – Monitor BizTalk MessageBox databases, BizTalk-specific SQL jobs, and BizTalk application health
- [Windows Server Agent][] – Monitor SQL Server host operating system (CPU, memory, disk, services, Event Log)
- [Azure Agent][] – Monitor Azure SQL Database alongside other Azure services (Functions, Storage, Key Vault, API Management)