Install Nodinite Database Monitoring Agent
Get started with the Nodinite Database Monitoring Agent and unlock seamless monitoring for SQL Server, Azure SQL Databases, and PostgreSQL. This guide walks you through each installation step, highlights key requirements, and ensures a smooth setup experience.
✅ Simple step-by-step installation process
✅ Supports SQL Server, Azure SQL Database, and PostgreSQL
✅ Clear guidance for service account and prerequisites
✅ Troubleshooting tips and direct support access
Use this guide to learn about how to install the Nodinite Database Monitoring Agent to achieve Monitoring of SQL Server, Azure SQL Databases, and PostgreSQL.
Nodinite v7.2.0 and Later (Recommended)
New 7.2.0
Database Monitoring Agent v7.2.0 and later should be installed using the Nodinite Portal-based scripted installation. This modern approach provides automated installation and configuration with minimal manual intervention.
Why Use Portal-Based Installation?
✅ Automates agent installation and configuration via PowerShell scripts
✅ Configures multiple agents simultaneously with consistent settings
✅ Eliminates manual MSI installations and reduces human error
✅ Centrally manages all environments from the Portal
✅ Includes AI Diagnostics New 7.2.0 for intelligent error analysis
✅ Supports .NET 10 runtime for modern platform performance
✅ Group Managed Service Account (gMSA) support for automated password management
Get Started with Portal-Based Installation
Follow the comprehensive Install Nodinite v7 guide to install the Database Monitoring Agent using the Portal-based approach. The Portal generates PowerShell scripts that install and configure the agent automatically.
Key Steps:
- Register your environment in the Nodinite Portal
- Select Database Monitoring Agent in the Agents configuration tab
- Configure agent settings (port, service account, database connections)
- Download the installation package with embedded PowerShell scripts
- Run the PowerShell script to install and configure automatically
Complete Portal Installation Guide - Step-by-step instructions with screenshots
Legacy Installation (Remote Servers Only - Not Recommended)
Warning
Deprecated: The MSI-based installation method is legacy and intended only for remote server installations where the Portal-based approach cannot be used. This method is not recommended for new deployments and will be retired in future versions.
Important
Version 7.2.0+ Users: If you are installing Database Monitoring Agent v7.2.0 or later, use the Portal-based installation method instead. The MSI approach below is for legacy v6 installations or remote servers only.
When to Use MSI Installation
Use this method only if:
- You are installing on a remote server that cannot be managed via Portal scripts
- You are maintaining a legacy v6 environment (upgrade to v7 recommended)
- You have specific infrastructure constraints preventing automated installation
MSI Installation Prerequisites
Important
You must be a local administrator to have the right to install Windows Services.
Before you begin
Make sure you comply with the prerequisites.
Step 1: Start the installer
Double-click on the MSI file to start the installation of the Nodinite Database Monitoring Agent.
Example MSI file, you should download and use the latest official version
Click the 'Run' button to continue.
Step 2: Welcome screen
On successful execution of the MSI file, a Welcome screen presents:
Welcome screen for the installer
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 3: Custom setup
Select the components to install and select the destination path for the installation.
Custom setup options for the installation
Note
Default settings are recommended
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 4: Service Account Information
This is the account running the Windows Service.
Enter credentials:
- Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or a . (dot) as Domain.
- User: The name of the account.
- Password: The password for the account.
Note
The account must have 'Log on as Service Right'
Service account credentials for the Windows Service
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Insufficient Privileges
Error message when account information does not meet Prerequisites:
Insufficient privileges error example
If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!
Tip
Check the local event log if there are errors (both System and Application)
Step 5 Completed setup
The last step of the installation gives either a success or a premature exit:
Successful installation example.
Failed installation example: A failed installation renders a premature exit:
Premature exit example for failed installation
Click the Finish button to Exit and quit the installer.
Step 6: Add Agent as a new Monitoring Agent Configuration
When the setup has finished, the default text editor will open a file named 'README.txt'. This file contains the agent's connection details needed to add it as a Monitoring Agents.
Instructions on how to add the Database Monitoring Agent as a Monitoring Agents is detailed in a shared article, click on the link below to learn more:
Support
Contact our Support for additional guidance if you fail to resolve the installation problem.
Note
Additional information to aid the troubleshooting may exist in the Windows Event Logs..
Next Step
Add or manage a Monitoring Agent Configuration
Configuration of the agent
Update
Related Topics
Prerequisites for Database Monitoring Agent
Monitoring Agents
Uninstall