<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=204641&amp;fmt=gif">

dbWatch FAQ

dbWatch is a complete database monitoring and management solution for your database server farm. 

Proactive monitoring helps you identify and resolve potential issues before it becomes a serious threat to your system, helps tune your database infrastructure and optimize your database resource usage.

In this section we will answer some of the common questions asked about dbWatch.


dbWatch Installation, Licensing and Support

Yes, dbWatch offers 30 days free evaluation for 25 database instances of any platforms supported.

Fill out the form in the get started page to receive your evaluation license key. We can also extend license period upon request.


For tech support users can visit the support page or the forum page. Users can also access wiki.dbwatch.com for more reference materials or visit dbWatch.com/videos for more user guides.
dbWatch has various technical guides and installation guide available for download on the website: www.dbwatch.com/support.
You can also visit the dbWatch Wiki for system guide and the videos page and our youtube channel for more tutorials.
dbWatch supports almost all versions of Oracle, MS SQL Server, MySQL, MariaDB, PostgreSQL, Sybase and Azure.
The dbWatch server can be installed on Windows, Linux or MacOSX.
Yes, we do count each pluggable database as an instance, so it will require 1 license per pluggable database.
So a container with 3 pluggable database count as 3 instances/licenses.

No, dbWatch is agent-less and does not consume too much resources, it would not affect your entire database operations.
It only installs a few packages on your database instances to collect the needed performance statistics for monitoring.

dbWatch Architecture & Configurations

dbWatch is built on standard, three-tier client server architecture:
  • Database monitoring tasks are stored inside the monitored database instance (dbWatch Engines).
  • The application server (dbWatch Server)
  • Client GUI (dbWatch Monitor Client).

dbWatch does not use OS based agents, we access the database servers directly.

In addition, dbWatch includes extensions to support integration with third-party systems management solutions like SCOM or Nimsoft
To know more about the dbWatch architecture visit this page.
Each dbWatch server can  support 250 connections for Windows ( and 500 if installed on Linux. This is an OS limitation in Windows and Linux.
So, if you have 1000 database instances to monitor, you’ll be needing 4 dbWatch servers  (on Windows) to monitor all those instances.
With dbWatch you can add as many dbWatch servers as you need to connect to as many instances as you need.  Typically you will have one dbWatch server in each location or network if running large dispersed or partioned sites, or use as many servers as you need if you manage hundreds or thousands of database instances.
dbWAtch is built from the ground up with a distributed, scalable architecture. dbWatch engines are distributed on each instance, and statistics are kept locally on each instance. This avoids building huge central repositories. This keeps network traffic down and scales eztremely well.
All reports, views and dbWatch tasks are delivered in source form and may be customized by the end-user, partner or dbWatch.

Custom changes for a single customer is documented separately.
If and when integrated into main product it will be moved to online documentation on the wiki page under release notes.
None required. dbWatch uses JDBC to connect to instances (or SSH in case of Oracle).
dbWatch can also be managed through a Command Line Interface (CLI)
dbWAtch is built on a istributed, scalable architecture.
dbWatch engines are distributed on each instance, and statistics are kept locally. This avoids building huge central repositories and minimizes impact within the monitored database and within the network as it retrieves minimal data as possible.

dbWatch is an agent-less monitoring software. It deploys the dbWatch framework in the monitored instance which are composed of procedures that retrieve the status and performance statistics needed by the dbWatch server.
Yes, users can receive alerts thru SMS or Emails. Alerts can be fully customized  and configured as to who receives what, how and when.
dbWatch can also send signals or alerts to 3rd party infrastructure monitoring tools like SCOM, Nimsoft and others.
dbWatch use fine-grained, role based-access controls.
Administrators can easily grant roles to specific users within dbWatch and limit their access within the application and its different modules.
Yes, dbWatch supports high availability and cluster monitoring for Oracle and Microsoft SQL Server
 Yes, dbWatch provides a variety of pre-configured performance and health reports. Users are also allowed to create new report templates or customize the existing ones. Refer to dbWatch Reporting.
Yes, dbWatch can automatically schedule and  distribute reports within the organization thru email or SMS. Users can also configure repository for reports where all generated files will be stored.
Yes, dbWatch supports role-based access and integration with enterprise directories such as Active Directory authentication.
 dbWatch also supports Kerberos authentication, OS authentication and SSH Authentication.

Yes, To ensure the privacy of the user sessions, dbWatch wraps all communication
between the monitors and the servers in SSL.

Yes, dbWatch provides cross domain access and security features to allow consultants at any given moment or a specified time schedule based on the enterprise SLA.

Key Features:


  • Monitor MS SQL Server, Oracle, MySQL, Postgres & Sybase

  • Database Farm Management

  • Complete Workflow Solution

       - monitor, analyze, manage instance & advanced reporting

  • Automate Monitoring and Maintenance

  • Customizable Dashboards

  • Multi-site and Hybrid Cloud Support

  • Scalability and Security



Get your FREE dbWatch Control Center evaluation now!