FAQ

In this section – you will find the frequently asked questions regarding the dbWatch.

• Do you offer an evaluation copy of your product?
  - Yes, we do offer a 30-day trial for a maximum of 25 database instances of any database platforms supported. We can also extend upon request.

• How do you handle customizations unique to User? Describe methodology, tracking, tools used, User access to tracking of customizations, requests, issues reported.
  - All reports, views and task/alerts (stored procedures) are delivered in source form and may be customized by end-user, partner or dbWatch

• Describe your roadmap and strategy for upgrades, etc for business/operational upgrades and technology upgrades.
  - We introduce new technology and major functionality in major releases bi-annually. Minor bug-fixes and
  enhancements are introduced continuously. Minor releases occur approximately every 3 months. Urgent
  bug-fixes released when done.

• Do you add custom changes to your on-line documentation? Do you provide documentation on your changes?
  - Custom changes for a single customer is documented separately. If and when integrated into main
  product it will be moved to online documentation.

• Provide details on the product architecture like client-server, n-tier, web-based, etc.
  - dbWatch is built on standard, three-tier client server architecture, with database monitoring tasks inside the monitored database instance (dbWatch Engines), the application server (dbWatch Server), and client GUI (dbWatch Monitor Client). In addition, dbWatch includes extensions to support integrating with third-party systems management solutions.

• What are the installation requirements in terms of software and hardware? Provide details in terms of physical/virtual machines support? Does the product/system include a setup wizard that guides the installation/configuration process?
  - Please see hardware requirements and prerequisites within the wiki page.
  Yes, we do support VMware virtual servers. Yes, the product has an easy to follow setup wizard that guides you throughout the installation. It will take less than 5 minutes to finish the dbWatch installation.
  We also have a step by step guide within our wiki page – www.wiki.dbWatch.com or visit our YouTube channel (@dbWatch) for more video tutorials.

• What is your typical timeline for implementing your product in production? Describe your SDLC processes. Include details on the types of assistance for go live activities and communications.
  - dbWatch installation and deployment in small sites (<10 instances) can be done in a single day.
  Then add time depending on number of instances and number of dbWatch servers required. Large sites (>100 instances) may require 2 weeks of installation and configuration.
  Training of DBAs can be done in 1-3 days. Many training videos are available for self-study. (dbWatch.com/videos)

• Is the agent installed at the Kernel or application level? Can it monitor memory?
  - dbWatch is agentless. We can install a small schema on each instance for stored procedures and logging performance data, but this is not mandatory. We can work with or without local schema. Yes, dbWatch can monitor the CPU and memory usage of your database instances.

• What integration protocols are required to connect with your product (i.e. SOAP/HTTPS, REST, and RPC)?
  - None required. dbWatch use JDBC to connect to instances (or SSH in case of Oracle)

• Does the solution integrate with third-party ticketing systems?
  - We have integrations with many 3rd party applications like SCOM, Nimsoft, Tivoli, and others.
  (see technical documentation for complete list.)
  New integrations via email can be easily added.

• Does the solution support integration with non-DBMS authentication, authorization, and access control (AAA) security frameworks? These include LDAP, RADIUS, RSA SecurID, and operating-related AAA.
  - Yes, dbWatch supports Kerberos authentication, OS authentication, Active directory and SSH Authentication.

• Does the solution support role-based access and integration with enterprise directories RADIUS, and TACACS?
  - Yes, dbWatch supports role-based access and integration with enterprise directories such as Active Directory authentication.

• What kind of encryption is supported for data in transit and data at rest?
  - JDBC encryption. SSH encryption.

• Does the solution provide preconfigured reports?
  - Yes, dbWatch provides a variety of preconfigured performance reports. Users are also allowed to create new report templates or update the existing ones. Refer to pre-configured checks within this document.

• Can a report be distributed throughout the organization? Is this distribution electronic with auditable signatures and authorizations?
  - Yes, dbWatch can distribute reports within the organization thru email or SMS. Users can also configure repository for reports where all generated files will be dumped there.

• Does the solution support high-availability operations and failover?
  - Yes, dbWatch supports High availability and cluster monitoring.

• How does the solution separate groups of personnel for role segregation implementation?
  - DbWatch use 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.

• Online support portal that we can access with search capabilities?
  - For support users can contact support@dbwatch.com, users can also access wiki.dbwatch.com for more reference materials or visit dbWatch.com/videos for more user guides.

• Different kinds of documentation available – user documentation, system documentation, context based, etc.?
  - dbWatch has various technical guides and installation guide available for download on the website: https://www.dbwatch.com/dbwatch-support

• Does the solution proactively alert the administrators for any type of activity necessary? What types of alerts and notifications are supported (Syslog, SNMP, emails, and pagers, or custom classes for distribution of alerts)?
  - Yes, users can receive alerts thru SMS or Emails. dbWatch can also send signals or alerts to 3rd party infrastructure monitoring tools

• Describe how the system architecture can scale to support growth?
  - Each dbWatch server can only support 250 connections for Windows and another 250 for Linux.
  So, if you have 1000 database instances to monitor, you’ll be needing 4 dbWatch servers to monitor all those instances.
  Distributed, scalable architecture. dbWatch engines are distributed on each instance, and statistics are kept locally on each instance. This avoids building huge central repositories.

• Does the solution architecture support an agent-based or agent-less implementation on the database server?
  - dbWatch is an agent-less monitoring software. It deploys the dbWatch framework in the monitored instance which are composed of procedures that retrieve the performance statistics needed by the dbWatch server.

• What is the impact of the solution on the performance of monitored database servers or monitored database? What is the impact of the solution on network performance?
  - Distributed, scalable architecture. dbWatch engines are distributed on each instance, and statistics are kept locally. This avoids building huge central repositories. Minimizing impact within the monitored database and within the network as it retrieves minimal data as possible.

• What operating systems and databases does the agent support?
  - No agent.
  dbWatch supports Windows, Linux and MacOSX for dbWatch server.
  DbWatch support almost all versions of Oracle, MS SQL Server, MySQL, MariaDB, PostgreSQL and
  Sybase database platforms. See documentation for exact details.

• How do you charge for the Oracle pluggable database?
  - Yes, we do count each pluggable as an instance, so it will require 1 license per pluggable.
  So a container with 3 pluggable count as 3 instances/licenses.