Release notes

dbWatch Control Center 25.3.039 (2025-12-18)

Download

Important note

• Users running the dbWatch Web Server with anonymous access must update their token value after upgrading to this release. Until the token is updated you may experience authentication issues or inability to access the web interface. See Anonymous web access for more information.
• For customers still running dbWatch 12, upgrading to the latest version (25.3.x) requires first converting to version 25.2.x (released April 15, 2025).

Known issues

• The MS SQL Server 2005 platform is currently not supported in this release. This is due to changes and increased security requirements in the communication between the dbWatch Server and monitored database instances. For technical background, see MS SQL Server TLS requirements. There are plans to reintroduce support for SQL Server 2005 during 2026. SQL Server 2000 remains fully supported by dbWatch.
• In the Management section for the MS SQL Server platform, the “Kill All Sessions” option in the login, program, or database context menus is currently non-responsive. This will be fixed in a future patch following the current release.
• Weaknesses related to the collection of execution plans for SQL statements in the Performance module for the MS SQL Server platform remain unresolved. The first release in 2026 will include improvements addressing this, including logging of plan changes for specific SQL statements.

Security related improvements

• DBW – Migrated runtime to Java 24 for enhanced security and long term platform stability.
• DBW – Upgraded third party libraries and removed obsolete ones. (DEV 4, DEV 95)
• DBW – Cloud router access token no longer plaintext and has an optional “Hint” field.
• DBW – Worksheet authentication flushing issue addressed. (DEV 135)
• DBW – Improved encryption handshake protocol – Replaced legacy Diffie-Hellman with Elliptic Curve Diffie-Hellman (ECDH) using secp256r1 and added HKDF-based AES key derivation with SHA-256. Simplified supported ciphers to AES/GCM for stronger security and better performance.

Usability and Administrative related improvements

• DBW – Can now set User expiry date. (DEV 109)
• DBW – “Copy to clipboard” menu added when instance connection errors occur. (DEV 93)
• DBW – Global component load time display.
• DBW – Syntax verification before resource upload
• DBW – Status text on mouse hover on a status table cell
• DBW – Deletion of a security group/role while in use is no longer allowed. (DEV 121)
• DBW – Local job reports now support admin based syntax (DEV 81)
• DBW – Improved error reporting for task installation/upgrade failure.
• DBW – Assigning an exhausted license to an instance no longer possible.
• DBW – Engine Authentication now displayed in instance configuration.
• DBW – Jobs can now have a “manual” schedule, meaning they will not run unless manually triggered.
• DBW – Changing to a license that does not include all used functionality will give a warning.
• DBW – Instance configuration “Save Changes” question less annoying.
• DBW – Filter field now available in management views.
• DBW – Optional text area in management headers
• DBW – Resolved issue with incorrect OK reporting when testing access points. (DEV 136)
• DBW – Self deletion of logged in user blocked. (DEV 97)
• DBW – Fix in offline task topic handling when system is in offline mode. (DEV 89)
• DBW – Bug when handling job parameters overrides in templates.
• DBW – Buggy sorting of view tabs in management.
• DBW – Selection of instance Worksheet/Management from Monitoring more robust.
• DBW – Now possible to delete the last cloud router access token

Performance and Stability improvements

• DBW – Added caching of hostname property resolution to improve performance. (DEV 83)
• DBW – Improved Reconnection handling of no engine instances
• DBW – Improved driver handling in instance creation & test connection flows. (DEV 106)
• DBW – Added optional manual node network cost configuration for mesh routing. (DEV 131)
• DBW – Node network cost calculation implementation to assess node capacity. (DEV 131)
• DBW – Introduced version cutoff handling in connection logic. (DEV 100)
• DBW – Installer migrated from Install4j to MSI for Windows platform.
• DBW – Bugfix when handling multiple versions of the same task in a resource bundle.

Minor bugfixes and improvements

• DBW – LineCharts can now handle dates (and not just datetime) on the time axis.
• DBW – LineChart did not handle resultsets where not all columns were plotted.
• DBW – Compatibility resolving in Monitoring tabs
• DBW – Handling of name/role collisions in the Domain Configuration dialog. (DEV 134)
• DBW – Fixed buggy report layout that caused charts not to load. (DEV 81)
• DBW – Fixed “header¬icon misalignment” in management filters. (DEV 94)
• DBW – Bugfix for special characters in regex handling of FDL-like function. (DEV 104)
• DBW – Handling of dynamic values in management dialogs.
• DBW – Bug when handling job parameters overrides in templates.
• DBW – Buggy sorting of view tabs in management.
• DBW – Bugfix for Copy cell with large cell content

Platform specific fixes and improvements

• MS SQL Server – Push Backup to Shared Devices [DEV-8]. Performs scheduled backups of selected databases to a shared network backup device, making them available for remote restore by other SQL Server instances.
• MS SQL Server – Pull Backup from Shared Devices [DEV-9]. Job which restores selected databases from a shared network backup device created by another SQL Server instance, supporting cross-instance recovery workflows.
• MS SQL Server – MS Management – Backup device administration [DEV-10]. Enhancements have been made to the management of backup devices within the MS SQL Server platform in the Management section of dbWatch. These improvements were necessary to support the introduction of new dbWatch jobs \(“Push Backup to Devices” and “Pull Backup from Devices”\), where efficient handling of a large number of backup devices and clear visualization of their contents are critical.
• MS SQL Server – SQL Statistics for MS SQL Server [DEV-16]. A new column has been added to the table containing query plans. This enhancement improves performance when retrieving data from the table during analysis in the Management section of dbWatch Monitor, enabling faster and more efficient access to query information.
• MS SQL Server – S&C non-compliance issues table fix [DEV-17]. Fixed an issue in the Farm View module under Security and Compliance where the table “MS SQL Server instances with no [job-name] issue” previously failed to display data. The table now correctly lists all instances that are compliant and have no issues detected by the specified job.
• MS SQL Server – UNLOCK login menu [DEV-18]. A new context menu has been added in the Management module for the Microsoft SQL Server platform (version 2012 and above), allowing administrators to unlock logins directly from the UI. Additionally, two new menu options have been introduced to configure the `CHECK_POLICY` and `CHECK_EXPIRATION` settings for SQL logins, making login management more accessible and efficient.
• MS SQL Server – IS_ONLY_BACKUP column in Backup view [DEV-19]. A new column, `is_copy_only`, has been added to the backup view in Management for Microsoft SQL Server. This allows users to identify whether each backup was created using the COPY_ONLY option. This will allow you to easily distinguish between regular and copy-only backups directly in the table.
• MS SQL Server – Farm-Views, Cross-Instance Database Transfers [DEV-20]. New farm-level views have been added in dbWatch Monitor to improve visualization and control of database movement across SQL Server instances. These views are designed to support workflows based on the “Push Backup to Shared Devices” and “Pull Backup from Shared Devices” jobs.In environments with multiple SQL Server instances and a high number of databases, the new views provide a structured overview of which databases are being exported or restored, on which instances, and their current status. This enables better operational control, traceability, and insight into large-scale cross-instance recovery and migration processes.
• MS SQL Server – Fix for Missing SQL Text in SQL Statistics Job [DEV-26].A bug was identified in the SQL Statistics job where some performance statistics entries were missing the associated SQL text. This issue has now been resolved, and the job should be updated to include the fix in future releases. The root cause was related to incomplete handling of specific plan or cache scenarios. A new column was also added to the main table that shows the first 1000 characters of an SQL text.
• MS SQL Server – Session SQL activity snapshot [DEV-35]. This job collects detailed information about currently active SQL sessions by joining data from master.dbo.sysprocesses, master.dbo.sysdatabases, and sys.dm_exec_requests. It extracts session context such as login name, host machine, database, and client program, and correlates it with currently executing SQL statements. The purpose of this job is to complement the “SQL statistics” job, which tracks SQL handle-based performance but does not associate activity with session-level details. This provides more actionable insights into who is executing which queries, and from where — particularly useful for troubleshooting or live monitoring.
• MS SQL Server – SQL Plan stat for MS [DEV-45]. The “SQL Statistics” job has been improved to more accurately retrieve execution plan values and associate them with the correct database. Additionally, enhancements have been made to the visualization of execution plan statistics in the Management section of dbWatch Monitor, providing clearer and more structured insights.
• MS SQL Server – AlwaysOn Database Backup Check [DEV-51]. Added new parameter exclude_copy_only_databases to the backup check job for AlwaysOn databases. This parameter allows copy-only backups to be ignored when evaluating backup status, ensuring that only regular backups are considered valid for compliance and alerting.
• MS SQL Server – Improve SQL statistics filtering [DEV-74]. Enhance the filtering of SQL performance statistics in the Performance module for MS SQL Server. Currently, users can sort resource-intensive SQL calls by metrics such as Logical/Physical reads, Logical writes, and Executions. With this improvement, it will be possible to visualize only the SQL calls originating from a specific database, providing more precise insight and easier troubleshooting when monitoring large multi-database environments.
• MS SQL Server – Improve SQL performance statistics visualization [DEV-64]. Enhanced the SQL performance statistics view in dbWatch Monitor (Management section for MS SQL Server). Individual SQL handle statistics now display all SQL calls grouped by handle ID in a dedicated column. Added charts for worker time and elapsed time to improve visibility and analysis.
• MS SQL Server – New job “SQL Workload collector” [DEV-66]. Collects key SQL Server statistics counters, including Batch Requests/sec, SQL Compilations/sec, and SQL Re-Compilations/sec. This job provides insight into overall query activity and query plan efficiency, serving as a basis for performance monitoring and trend analysis.. The enhanced job will provide the data foundation for a new graph in the SQL Performance module within the Management section of dbWatch Monitor.
• MS SQL Server – property ms_inst_names, FDL fix [DEV-105]. Resolved an issue where the property ms_inst_names used incorrect FDL syntax in the filter part of the FDL query, causing the query to fail.
• MS SQL Server – Missing device in “Restore database” menu [DEV-107]. Fixed an issue in the “Restore database” menu for the MS SQL Server platform where the default value for the backup device was missing. The menu now correctly preselects the default backup device to improve usability and prevent restore configuration errors.
• MS SQL Server – Improved database tree loading [DEV-133]. Enhancement to the Management view for MS SQL Server in dbWatch Monitor.
When an instance contains a very high number of databases (several thousand), opening the Databases folder in the tree view could previously cause long loading times.
With this improvement, only the first 1000 databases (with dbID < 1001) are initially displayed when expanding the Databases folder.
The remaining databases are now grouped into subfolders in chunks of 1000 databases each (e.g., 1001–2000, 2001–3000, etc.).
This change significantly improves responsiveness and usability in environments with a large number of databases.
• MS SQL Server – Scheduler view for SQL Server Agent Jobs [DEV-138]. There is a bug in the Scheduler view under
Management → Server Instance → SQL Server Agent → Jobs → Schedules, where selecting “Show jobs using schedule” always returns “No data”, even when jobs are correctly linked to the schedule. The issue occurs due to conversion errors in columns such as next_run_date and next_run_time, which are stored as integers in SQL Server and are not properly converted during view rendering.
• MS SQL Server – Optimization of database size query [DEV-140]. The SQL query used to visualize database size metrics in the Management section (graph and details view) has been optimized (MS SQL Server platform). The previous version of the query consumed excessive resources on SQL Server instances with a large number of databases (typically over 1000). This caused unnecessary CPU and I/O load during data retrieval. The new version significantly reduces overhead by improving query logic and limiting expensive operations across large datasets.
• MS SQL Server – Conversion from 12 to CC [DEV-36]. The conversion procedure from dbWatch 12 to dbWatch Control Center has been improved to include a safeguard: it will now skip the conversion of dbWatch 12 data if the old system has not been used for a long time. This prevents unnecessary or outdated data from being migrated, ensuring a cleaner and more relevant setup in dbWatch Control Center.
• MS SQL Server – DB uptime [DEV-37]. New parameter “max rows per table” allows dynamic control over how many rows are shown in reports, keeping output concise. Several tables in the report now include clearer descriptions to improve interpretation. The procedure now detects and corrects data inconsistencies caused by migration from dbWatch 12 to Control Center.
• MS SQL Server – Log Shipping Monitoring [DEV-43]. The two log shipping monitoring jobs – one for the primary node and one for the secondary node – have been updated with improved support for the ignore databases parameter. You can now use the percent sign (%) as a wildcard character to match multiple database names.
• MS SQL Server – Session SQL event collector [DEV-47]. A new job which collects performance statistics from the dbWatchSessionStatsXE Extended Events session. It captures long-running SQL batches and RPC calls along with relevant session and database information. Complements the “SQL statistics” job by adding visibility into who is executing what.
• MS SQL Server – Management views for EVENT SESSION statistics [DEV-48]. New entry views in dbWatch Management provides access to the statistics captured by the Extended Events session and gathered by “Session SQL event collector“ job, displaying in a familiar layout for easy comparison and combined analysis.
• MS SQL Server – Blocking statistics – enhancement [DEV-49]. Adds `“capture threshold”` to optionally persist sub-threshold blocking sessions (recorded with OK severity) for trend analysis, in addition to existing 2 parameters. Default for the new parameter is disabled (0) to preserve current behavior unless explicitly enabled.
• MS SQL Server – Backup – ignore copy-only [DEV-50]. Added new parameter “exclude copy only databases“ to control whether copy-only backups should be considered when evaluating the last backup time. When enabled, only regular backups are used in the check; copy-only backups are ignored. This applies to both jobs, “Database backup“ and “Database log backup“.
• MS SQL Server – Backup all databases [DEV-52]. The reports for the “Backup all databases” and “Backup all transaction logs” jobs have been improved and made more flexible with a new parameter, backup history, which controls how much historical data is displayed in graphs and tables.
• MS SQL Server – Enhance Lazy Writer and Checkpoint Statistics job [DEV-68]. Improve the existing Lazy Writer and Checkpoint Statistics check by adding collection of the Free List Stalls/sec performance counter. This enhancement will provide deeper insight into buffer pool performance and memory pressure conditions, enabling more accurate monitoring and troubleshooting in dbWatch Monitor.
• MS SQL Server – Update default Job template [DEV-76]. The default job template has been updated to include the new SQL Workload Collector job. This ensures that the collector is available by default in new installations.
• MS SQL Server – Bug in Autogrowth Settings job [DEV-124]. Bug fix in the Autogrowth Settings job procedure where parameter values (expressed in MB) were compared with storage values for database files (expressed in KB).
• MS SQL Server – The comparison incorrectly divided by 1000 instead of 1024, leading to inaccurate evaluations of autogrowth thresholds. The job report has also been updated for clearer indication of which values are expressed in KB and which in MB.
• MS SQL Server – Improved visualization of Session Performance data [DEV-127]. Enhance the visualization of Session Performance data in the Management section of dbWatch Monitor. The goal is to make it easier to identify which programs, hosts, and logins were connected to the SQL instance during a given time period. The updated view should provide clearer filtering and grouping of session data to help users quickly understand connection patterns and activity over time.
• MS SQL Server – Fix permission validation in Management menues [DEV-144]. Several Management-level actions in dbWatch Monitor—such as “Kill session” and other interactive commands—are incorrectly checking only for read privileges instead of requiring the appropriate write/execute permissions. As a result, users without sufficient privileges may see menu options they should not be allowed to use.
• MS SQL Server – Farm CPU usage graphs [DEV-65]. Implement graphical (experimental ) visualization in Farm views to display historical CPU usage aggregated from multiple MS SQL Server instances. This enhancement will allow users to monitor and compare CPU consumption across servers in a single consolidated view.
• MS SQL Server – Engine script – MS SQL Server [DEV-108]. Enhanced the engine script for the MS SQL Server platform to handle invalid or missing default data and log paths retrieved from the Windows registry during dbWatch database creation. If the registry paths are incorrect, the script now catches the exception and creates the database files in the same location as the model database, using its default file paths.
• MS SQL Server – Timeout settings for “AlwaysOn transaction log backup” job [DEV-116]. Extended timeout settings for the “AlwaysOn transaction log backup” job. The current timeout threshold can cause premature job failure or false alerts.
• MS SQL Server – Update Major Version Properties for SQL Server 2025 Support [DEV-159]. Enhance the major-version detection properties for Microsoft SQL Server to correctly identify and return version information for SQL Server 2025. This update ensures accurate classification and compatibility across all relevant dbWatch modules that rely on version-based logic
• MS SQL Server – Improved Missing Index Handling in SQL Performance Module [DEV-152]. Enhance the SQL Performance module to better parse and visualize missing index information. Add support for generating recommended index scripts directly from the UI.
• MS SQL Server – “View Last 10 SQLs” for Blocking Sessions [DEV-156]. Enhancement to the blocking session management view: both inst_id and sql_id have been added to the “View last 10 SQLs” context menu option. This provides better traceability and improves troubleshooting of blocking chains.
• MS SQL Server – Brent Ozar module [DEV-145]. A new monitoring job that detects which “Blitz” procedures (e.g., sp_Blitz, sp_BlitzIndex, sp_BlitzCache) are installed on a SQL Server instance, in which databases they reside, and whether duplicate or inconsistent installations exist. In the Management section, users should be able to view, manage, and optionally execute these procedures. The Farm View should provide an overview of which SQL Server instances have Blitz procedures installed, including version information and any discrepancies.
• MS SQL Server – New FDL Property: default_windows_domain [DEV-153]. Add a new FDL property named default_windows_domain for the MS SQL Server platform. The property should retrieve and return the default Windows domain name by using the default_domain() function.
• MS SQL Server – New “max databases” parameter for Index usage statistics job [DEV-132]. Introduce a new parameter max databases to the job Index usage statistics (all databases). The parameter defines a threshold for the maximum number of databases on an instance where the job should be executed. The job is primarily designed for environments with a limited number of databases. On systems with a very large number of databases (several thousand), calls to sys.dm_db_index_physical_stats can become too resource-intensive and lead to unnecessary load on the SQL Server instance. By adding this parameter, the job can skip execution when the database count exceeds the specified limit, improving performance and resource control.
• MS SQL Server – Update “MS SQL Server Patch Status” Job for Latest Releases [DEV-157]. Develop a new version of the MS SQL Server Patch Status job to include detection of the most recent cumulative updates and security patches (released up to November 2025) for SQL Server 2017, 2019, 2022, and 2025. The updated job should ensure accurate version mapping and improved reporting across all supported SQL Server editions.

• Oracle -Change compatibility for “SYS.AUD$ size” job [DEV-73]. Update the compatibility rules for the SYS.AUD$ size job in Oracle. It should no longer be possible to install this job on pluggable databases. Previously, it was incorrectly allowed, which resulted in false alarms when the job was deployed to pluggable databases.
• Oracle – Oracle space estimated [DEV-53]. The graph that previously displayed only the estimated allocated space for all data files has been improved. It now also includes the actual space used inside the files, so both allocated and used values are shown side by side for better insight.
• Oracle – Oracle Framework job [DEV-14]. The job now checks the expiration date of the dbWatch database user (for Oracle) and automatically resets the password before it reaches the expiration date. This improvement ensures that monitoring continues without interruption and prevents failures caused by dbWatch being unable to log in to the database.
• Oracle – Oracle Health Check Report [DEV-15]. The report has been enhanced with a series of visibility filters that prevent queries from being executed against instances when the underlying objects or tables are missing. Additionally, an initial table has been added to the report to display the status of each instance, providing an early indication of whether the report can be run successfully.
• Oracle – Oracle MOUNT properties [DEV-28]. We have updated the definition and handling of `dbWatch-properties` to improve compatibility with Oracle instances running in “MOUNT“ mode. These improvements ensure that the system no longer attempts to access views or operations that are unavailable in this state and reducing errors in dbwatch log files.
• Oracle – AUD$ table size check [DEV-29]. Enhanced the exception handling in the “AUD$ Table Size Check” job to make it more robust and stable. The job is now fully compatible with non-pluggable Oracle databases.
• Oracle – Delete AUDIT records [DEV-30]. Improved exception handling in the “Delete SYS.AUD$ data” job and ensured compatibility with non-pluggable Oracle databases.
• Oracle – Duplicate Alert Log Entries [DEV-31]. This development task addressed an issue where, in pluggable Oracle databases, rows from the alert log were being read multiple times. This could lead to the same error message being triggered repeatedly. The logic has been corrected to ensure that each alert entry is processed only once, improving accuracy and reducing noise in monitoring.
• Oracle – Oracle DataGuard [DEV-33]. This development task involved improvements across several monitoring jobs related to Oracle Data Guard instances. The updates covered key areas including apply time, sequence apply lag, gap detection, transport status, and startup time — resulting in more accurate and reliable monitoring of Data Guard environments.
• Oracle – Engine Compatibility for Selected Oracle Jobs [DEV-34]. This development task ensures that the following Oracle jobs — “Max datafiles”, “Max processes”, “Flash recovery space usage”, and “Datafile status” — are now compatible with instances that have the dbWatch-engine. This prevents them from being placed in the “undefined” group when a standby node becomes primary in a Data Guard environment.
• Oracle – Redo statistics [DEV-21]. A new version (v.3.61) of “Redo statistics“ job, which now includes, among other improvements, a report section that shows counts of redo log switches per day. Each row represents a specific hour and the number of switches recorded during that hour. The table is used to analyze daily and hourly trends in redo log activity.
• Oracle – Applied archive log gap status [DEV-23]. The dbWatch job “Applied Archive Log Gap Status” was updated to handle a specific error: numeric or value error: character to number conversion error. The fix ensures more robust parsing of input values. By default, the job analyzes only active archive log destinations, in line with standard Oracle configuration practices.
• Oracle – Dataguard Archive Sequence Apply Lag [DEV-24]. The job “Dataguard Archive Sequence Apply Lag”, intended to run on physical standby databases, has been improved to better handle non-standby environments. If executed on a database that is not in standby role, the job will now clearly report the current “database role” and will no longer raise a warning or alarm status in such cases. The job is renamed to “Dataguard archivelog apply gap”.
• Oracle – New FDL properties for Oracle sessions [DEV-77]. Implement new FDL properties for Oracle sessions, including sub-properties such as machine, logon_time, suser, status, program, and others. These properties should only apply to the Oracle platform and will enhance session-level monitoring and diagnostics within FDL.
• Oracle – Conversion from 12 to CC [DEV-36]. The conversion procedure from dbWatch 12 to dbWatch Control Center has been improved to include a safeguard: it will now skip the conversion of dbWatch 12 data if the old system has not been used for a long time. This prevents unnecessary or outdated data from being migrated, ensuring a cleaner and more relevant setup in dbWatch Control Center.
• Oracle – New properties for Oracle CDB and PDB [DEV-115]. New properties are needed for Oracle CDB and PDB databases to determine the correct target location for the dbWatch schema specification after a switchover or failover event. These properties should allow dbWatch to identify which container and pluggable database currently host the active schema and ensure automatic relocation or validation of the schema specification during role transitions in an Oracle Data Guard or RAC environment.
• Oracle – Improved Output for Primary Instances in “Replication Delay Alert” Job [DEV-160]. Enhancement of the Replication Delay Alert job to provide clearer and more complete output on primary instances.
• Oracle – Database uptime calculation in Oracle DataGuard environments [DEV-141]. Property definitions related to database uptime calculation have been reviewed and improved for Oracle DataGuard environments. The previous logic did not consistently account for role transitions (Primary – Standby) or temporary disconnections in DataGuard setups, which could result in inaccurate uptime reporting.

• PostgreSQL – pgBackRest backups [DEV-22]. Three dbWatch jobs which monitor the presence and freshness of full, differential, and incremental pgBackRest backups. Each job checks that at least one recent backup of the respective type exists, ensuring a complete and recoverable backup chain. The jobs rely on an external script that extracts backup metadata using ‘pgBackRest info —output=json’ and inserts it into a PostgreSQL table. This table does not need to reside in the `dbwatch` schema but must be accessible within the dbWatch monitored database.
• PostgreSQL – Standby marking for Patroni Secondary [DEV-158]. Add the standby arrow to Patroni Secondary instances.

• Azure – Azure DB – Rebuild indexes [DEV-40]. The “Rebuild Indexes” maintenance job for Azure single database instances has been updated with a new parameter: ‘rebuild_timeout’. This parameter defines the maximum number of seconds allowed for an individual index rebuild operation before it is automatically terminated.
• Azure – Improvement to Azure Performance Jobs [DEV-41]. The three Azure performance monitoring jobs – CPU, IO, and Log Write – have been updated with a new parameter: retry_threshold. This parameter controls how many times the job will retry fetching data before reporting an error. The enhancement helps prevent false alarms caused by transient connectivity issues or external Azure-related delays, ensuring more robust and reliable monitoring.
• Azure – Azure DML statistics [DEV-58]. The Azure database job responsible for gathering DML statistics had an error that prevented the test from being triggered. The issue has been corrected, and the job now runs and triggers the test as expected.

• DBW – Column width for “DB count” [DEV-87]. Updated the “DB count” column in dbWatch Monitor by adjusting its width for better readability and changing the column title to ensure consistent naming and visual alignment with other columns in the view.
• DBW – Offline instances in dbWatch Monitor [DEV-89]. Enhanced the visualization of offline instances in dbWatch Monitor. When an instance is offline, only the information available from the dbWatch Server side is displayed. This provides a clearer and more accurate representation of instance status and available data
• DBW – instance_class property [DEV-143]. Introduce a new dbWatch FDL property instance_class for all supported database platforms (Oracle, SQL Server, PostgreSQL, MySQL, etc.). The property returns a concise, human-readable classification of the connected SQL instance’s architecture/topology and role (e.g., cluster/HA type and primary/secondary state). The value will also be used to auto-render an additional icon in dbWatch Monitor where appropriate.
• DBW – Minor improvements to Internal View [DEV-130]. Enhance the Internal View to improve clarity and usability when managing multi-domain dbWatch environments. The changes include small layout and visualization adjustments to make it easier to distinguish and navigate between domains and servers.

dbWatch Control Center (2025-04-15) / (25.2.x)

Download

New features

• PostgreSQL – Job “Database status”. This job monitors the availability status of databases in a PostgreSQL instance by checking the datallowconn column in the pg_database system catalog. This job is supported with dbWatch engine installed.
• PostgreSQL – Job “Database status alert”. This job monitors the availability status of databases in a PostgreSQL instance by checking the datallowconn column in the pg_database system catalog. This job is supported without dbWatch engine installed (no dbWatch database schema).
• MS SQL Server – job “MS SQL Server patch status”, added patch information from Microsoft Update Catalog up to Mars 2025 (patch CU18 for 2022, CU32 for 2019 and SP Azure for 2017).
• Redhat release available – see install guide

Bugfix

• Oracle – Job “Instance alert log” Now compatible from Oracle 12.2 and not 12.1 (due to too many rows returned by V$DIAG_ALERT_EXT). Parameter “max_lines” changed to “max lines”. The job “Instance alert log 11″ is designed for use with Oracle versions 11 and 12.1.
• Sybase ASE – Job “User connections check”, now checking “number of user connections” parameter value.
• Sybase ASE – engine, error when upgrading jobs. The version number does not change.
• PostgreSQL – Job “SQL Statistics”. A bug was fixed where the job incorrectly collected SQL statement statistics based on high values of blocks read instead of blocks hit. This caused statements with low I/O (i.e., primarily served from cache) to be excluded from being collected. It now supports PostgreSQL version 17.

Improvements

• MS SQL Server – Improved several menus and enhanced usability in the Audit section of the Management module.
• Farm views – The Farm View for Maintenance jobs was also significantly improved, with better structure, clearer output, and enhanced documentation to help users interpret results more easily across instances.
• PostgreSQL – Job “Transaction statistics”. Exception handling was added to improve the robustness of the job and prevent unexpected failures. In addition, general code improvements were made to enhance readability and maintainability. A new parameter was also introduced: max databases per graph, which defines the maximum number of databases displayed in the report graphs.
• PostgreSQL – Job “Buffer cache reads per database”. Exception handling was added to improve the robustness. A new parameter was also introduced: max databases  per graph, which defines the maximum number of databases displayed in the report graphs.
• PostgreSQL – Management. The PostgreSQL Performance module has been enhanced to provide clearer and more informative insights. Most notably, Buffer Hit Ratio is now displayed both in the graph and in the accompanying data table, making it easier to interpret cache efficiency. In addition, the visual presentation of several other graphs has been improved, offering better clarity and consistency across the module. Documentation has also been updated to provide more context and guidance for interpreting the performance metrics.
• PostgreSQL – Management. The visualization of offline databases (where datallowconn = false in pg_database) has been improved. These databases are now clearly marked with an orange icon and the label “(OFFLINE)” next to their names. Additionally, new menu options have been added to bring databases online or take them offline, making it easier to manage connection permissions directly from the interface.
• PostgreSQL – Job “Backup check – WAL“. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Backup check – pg_dump”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “DBMS uptime”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Schema growth collector”. Excludes “offline” databases (the datallowconn column in the pg_database system catalog is set to false).
• PostgreSQL – Job “Vacuum alert”. Excludes “offline” databases (the datallowconn column in the pg_database system catalog is set to false).
• PostgreSQL – Job “Log size statistics”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Schema growth statistics”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Tablespace growth and information”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Database growth rate and info”. Exception handling was added to improve the robustness of the job, and excludes “offline” databases.
• PostgreSQL – Job “Buffer cache statistics”. Exception handling was added to improve the robustness of the job.
• PostgreSQL – Job “Disk block hitrate”. Exception handling was added to improve the robustness of the job, and excludes “offline” databases.
• PostgreSQL – Job “Disk block reads per database”. Exception handling was added to improve the robustness of the job, and excludes “offline” databases.
• PostgreSQL – Job “Table and index scan statistics”. A new parameter was also introduced: max objects per graph, which defines the maximum number of objects displayed in the report graphs.
• PostgreSQL – Job “Replication delay alert”. No longer reports unnecessary delay information for the primary instance in a Patroni cluster, and now simply identifies it as the primary

dbWatch Control Center (2025-02-12) / (25.1.x)

Download

If you are using anonymous web access for integration, there are some changes in how this is handled. See details.

New features

• MS SQL Server – new job “Logins default database check”, this procedure performs two checks. “Sysadmin Logins Default Database Check” which verifies that all logins with sysadmin privileges have their default database set to master, and “Default Database Validity Check” which identifies logins with a default database that is either not online or does not exist. The results provide insights into potential misconfigurations that could impact login functionality or administrative best practices (category: Security).
• Azure database – new job “Rebuild indexes”, a new maintenance job for rebuilding indexes on a single Azure database.
• DBW – FDL force function. Will flush and force a new resolving of a single fdl property.
• DBW – Job post FDL execution (for flushing properties)
• DBW (experimental) – USL scheduling and parameter handling
• DBW (experimental) – USL from no engine jobs
• DBW (experimental) – USL can now set metadata
• DBW (experimental)) – Non-database instances (target)

Bugfix

• Oracle – job “RMAN backup status”. Job fails during execution with “ORA-01403: no data found” (new version 2.66).
• Oracle – job “Buffer cache statistics” upgrade to version 2.3 failed in RAC environments.
• Oracle – job “Instance alert log” missing sys.dbw$dbgalertext view and select privilegies for dbwatch database user. Now using …. view.
• MS SQL Server – job “Database growth rate (aggregated)”. This job failed during installation on database instances with case-sensitive collation.
• MS SQL Server – job “Query Store status” exception with cursors on instances with multiple character sets (collations).
• MS SQL Server – job “Autogrowth settings” exception with cursors on instances with multiple character sets (collations).
• MS SQL Server – job “Index usage statistics (all databases)” exception with cursors on instances with multiple character sets (collations).
• MS SQL Server – job “Update index statistics” exception with cursors on instances with multiple character sets (collations).
• MS SQL Server – Agresso jobs support now database in AlwaysOn cluster
• MS SQL Server – Create local database on existing instance in AlwaysOn cluster
• DBW – Graphical bug in the SQL Worksheet that caused a lot of CPU usage while waiting for result
• DBW – properties import flush bug. Properties that were imported could take a while to appear.
• DBW – No engine job import caching issue. Imported jobs were not visible for up to minute after import.
• DBW – Delete node “ghost” issue. Nodes that were deleted from the domain, still appeared on some Monitors as a disconnected node.
• CCC – Certificate refresh issue. Privilege changes where not reflected in the CCC node certificate.

Improvements

• All DBMS platforms – job “Instance restart alert” has been improved to handle negative restart times (which are not supposed to occur) by recalculating them.
• Oracle – job “Tablespace free space”, new parameter, query_timeout
• Oracle – job “SYS.AUD$ size”, job has been improved to provide more descriptive feedback if the database instance is not in the OPEN state.
• Oracle – Global report “Health check report for Oracle”, presentations are generated according to the installed jobs, ensuring no errors occur if tables are missing from the dbWatch schema.
• MS SQL Server – job “Page verify option” job has been improved to record changes made to a database’s PAGE_VERIFY setting. It includes details such as the time of the change and the old/new PAGE_VERIFY value.
• MS SQL Server – job “SQL statistics” job has been improved to record missing index statistics. Additionally, the Farm view “SQL statistics job – execution statistics” has been extended to display the total number of missing indexes recorded and the timestamp of the most recent entry.
• MS SQL Server – job “Update index statistics”, added a new parameter which controls whether both column statistics and index statistics should be updated during the execution of the UPDATE STATISTICS operation.
• MS SQL Server – job “Wait statistics”. In this job, a clustered index was created on the historical table dbw_wait_stat_histr to reduce user_scans and improve query performance. This change aims to enhance the efficiency of data retrieval from the dbWatch history table.
• MS SQL Server – job “Index usage statistics (all databases)”. This job has been optimized to improve execution time in environments with a large number of databases (several hundred databases per instance). The improvements ensure more efficient performance and reduced runtime in such scenarios.
• MS SQL Server – job “DBCC CHECKDB“, improved exception handling
• MS SQL Server – job “Auto growth event collector” improved visualization of event data in the local report
• MS SQL Server – job “MS SQL Server patch status”, added patch information from Microsoft Update Catalog up to Januar 2025 (patch CU30 2019 and CU17 2022).
• PostgreSQL – Global report “Health check report for PostgreSQL”, removed chapters for Vacuum and Analyze.
• DBW – Can now have multiple menues from single table row
• DBW – Task autoupgrade more robust.
• DBW – Resource compatibility resolving optimization
• DBW – Manage Job Templates “loading” marking
• DBW – Web stability
• DBW – Web access tokens
• CCC – Can now work through Cloud Router
• CCC – FDL engine more robust
• DBW (experimental) – Editor image view zoom/scroll
• DBW (experimental) – Target now part of security and domain layout

dbWatch Control Center (2024-11-26)

Download

New features

• DBW – Bulk setting of SQL Worksheet authentications
• DBW – SQL Worksheet query timeout parameter
• DBW – AD integration now handles LDAP Signing
• DBW – CCC can now connect to non DC node
• DBW – FDL hash function
• DBW – FDL substring function
• DBW – FDL indexof function
• DBW – FDL length function
• PostgreSQL – Engine installation can now create dbWatch database

Bugfix

• DBW – CCC service command more robust
• DBW – New/moved instance refresh bug when using Cloud Router
• DBW – Monitor status circle refresh bug
• DBW – SQL Worksheet multi server query handling
• DBW – SQL Worksheet multi statement result handling
• MS SQL Server – job “Suspect pages”, compilation error on 2005 platform.
• Oracle – job “RMAN backup status”, block_change_tracking column, varchar to small.
• PostgreSQL – problems installing jobs “Vaccum tables”, “Vacuum alert” and “Analyze tables” with dbWatch-no-engine monitoring.

Improvement

• DBW – Web remote server access
• DBW – Heavy load stability improvements
• DBW – Job templates, use latest task version when resolving parameters
• DBW – Improved error reporting when file privileges prevent config save
• DBW – Node privilege changes now triggers certificate renewal.
• DBW – CCC now handles absolute paths to scripts
• DBW – Can now uninstall no-engine jobs that are no longer compatible from Manage Jobs view
• DBW – AD integration now handles multiple AD servers
• DBW – Improved performance of FDL compare function
• DBW – Now cleans old system event messages
• MS SQL Server – job “DBCC CHECKDB“, improved exception handling when main procedure terminates abnormally. Added two new parameters “return status when terminated abnormally”. This parameter defines the return status (ALARM – 2, WARNING – 1, or OK – 0) when the dbWatch main procedure terminates unexpectedly. An abnormal termination refers to errors with a severity level of 20 or higher, which can cause the entire procedure to terminate without entering the CATCH block.
  In such cases, the dbWatch job will only return information that it was terminated uncontrollably, without any details about the DBCC execution. Upon the next successful execution of the procedure, it will provide feedback
  on which database caused the issue. The parameter “keep WARNING/ALARM status” controls the duration (in hours) for which the job will retain a WARNING or ALARM status following the occurrence of such an event.
• MS SQL Server – job “Reorganize indexes”, improved exception handling when main procedure terminates abnormally.
• MS SQL Server – job “Rebuild indexes”, improved exception handling when main procedure terminates abnormally.
• MS SQL Server – job “MS SQL Server patch status”, added patch information from Microsoft Update Catalog up to November 14, 2024.
• Oracle – job “RMAN archivelog backup status”, new parameter “return status when ARCHIVER STOPPED“.
• MS SQL Server – Improved Farm views for Maintenance jobs.
• MS SQL Server – job “AlwaysOn transaction log backup alert”, the job provides improved feedback on last transaction log backups information when not all nodes in the AlwaysOn cluster are accessible.
• MS SQL Server – job “AlwaysOn database backup alert”, the job provides improved feedback on last full backups information when not all nodes in the AlwaysOn cluster are accessible.

dbWatch Control Center (2024-10-07)

Download

Improvements

• MS SQL Server – Job “Database disk capacity”. New parameter “combine thresholds”. This parameter allows you to combine the conditions of both the “alarm threshold (percent)” and “alarm threshold (MB)” or “warning threshold (percent)” and “warning threshold (MB)” parameters. When set to “YES“, an alarm/warning will only be triggered if both the percentage and MB threshold values are exceeded simultaneously. This setting provides an additional level of control, ensuring that alarms/warnings are only activated when both thresholds are surpassed, minimizing false positives and unnecessary alerts.
• MS SQL Server – Management, added availability group (AG) column to database statistics view and new view for AlwaysOn databases

Bugfix

• MS SQL Server – Job “framework”. Older versions of framework could not be upgraded in version 2.8 (fix in version 2.81). Internal use only.
• Oracle – Job “Extent fragmentation”. Fix for property “length”.
• Oracle – Error when installing engine-jobs with status.

dbWatch Control Center (2024-09-18)

Download

New features

• DBW – Email lost connection reminder
• DBW – FDL todate has format option
• DBW – Installing/Uninstalling jobs now in notes
• DBW – Remote Support
• DBW – Custom Monitoring pause
• DBW – Custom Alerting pause
• DBW – FDL empty/nonempty functions
• Oracle – job “RMAN ARCHIVELOG backup status alert” which can be used if no dbWatch schema exists.
• MS SQL Server – job “Deadlocks event collector”. Collects deadlocks event statistics from Microsoft SQL Server Extended Event Log files. If configured, a warning or alarm can be triggered when a deadlock is detected.
• MS SQL Server – Management, new “Deadlocks history” view.
• Sybase – SQL performance module (LICENSED)
• MS SQL Server – new sub farm view, “tempdb space usage” in “Resource overview”
• Farm – new “Uptime statistics” farm view displaing uptime statistics and maintenance periods statistics.

Improvements

• DBW – Global report item active
• DBW – Global report multi column layout
• DBW – Extension info i separate log
• DBW – Timeout in property fdl steps
• Sybase – Better SQL error reporting
• DBW – Warning when installing/uninstalling jobs when template in use
• DBW – Added uptime to About dialog
• DBW – Network stability
• MS SQL Server – job “MS SQL Server patch status”, ignores “Support end date” and use only “Extended support end date” in Security and Compliance overview.
• MariaDB – Management, added new graphs in SQL Performance module (“Session load”,“Memory usage”, “InnoDB data cache”)
• Sybase – Improved “Test DML-DDL performance” job with multi test series.
• MS SQL Server – job “AG synchronization lag”, new parameter “ignore events”, this parameter makes it possible to “skip” a warning or an alarm (one or more times) during initial synchronization lag detection.
• MS SQL Server – job “SQL statistics” improved procedure execution time.
• MS SQL Server – job “Databases NOT IN USE collector” has two new parameters enabling collecting statistics for additional databases with higher activity.
• Oracle – job “Buffer cache statistics”, new parameter “graph time range”, determines how many days back from the current date the data should be visualized in the report graphs.
• Oracle – job “Framework”, checks and/or removes date records in dbwatch schema if the clock on the database server has been moved forward in time.
• MS SQL Server – job “Framework”, checks and/or removes date records in dbwatch schema if the clock on the database server has been moved forward in time.
• Oracle – job “Database uptime”, two new parameters enabling adding and removing maintenance periods.
• MS SQL Server – job “Database Server uptime”, two new parameters enabling adding and removing maintenance periods.
• MS SQL Server – job “High activity monitor”, new parameter “graph time range”, and improved local report.
• Oracle – job “CPU load”, Better calculation of CPU consumption.

Bugfix

• Sybase – handling of multiple result sets
• DBW – issues in dictionary save
• DBW – Management chart height issue
• DBW – Reset password file privilege issue
• PostgreSQL – Handling of escape characters in password
• DBW/Web – New dashboard issue
• DBW – Compatibility issue for newly imported global report
• DBW – Edit scheduled report, save bug when tree is filtered
• DBW – Rare Monitor hang bug
• Oracle – job “RMAN backup status alert”, wrong date sorting, and now checks only input type “DB FULL“ and “DB INCR“.
• Sybase – job “Database growth rate”, report now showing all growth statistics with correct date format.
• Sybase – job “Framework” Upgrade with case sensitives collations fails.
• MS SQL Server – job “Transaction log size check” error: Divide by zero error encountered. Error line: 109. Pos: 04.
• MS SQL Server – job “Database Server uptime” error in report for case sensitive dbwatch database.
• MS SQL Server – job “MS SQL Server patch status”, empty “Details” column if newer patches installed.
• MS SQL Server – Management – node “Uptime statistics”, fix for case sensitive dbwatch database
• Oracle – job “Buffer cache statistics” Divide by zero error encountered. Bether exeption handling.
• MS SQL Server – job “Database Server uptime”, fix for case sensitiv dbwatch database.

dbWatch Control Center (2024-05-06)

Download

New features

• DBW – Editable glabal report name
• DBW – Global report – fdl parameter
• DBW – Http service management through CCC
• DBW – FDL tomillis function
• DBW – FDL set functions containsall/some/none
• DBW – FDL function toperiod
• MS SQL Server/Agresso module – “Agresso reports queue”, “Agresso help and temp tables”, “Agresso blob size collector”, “Agresso framework” (LICENSED)
• Oracle/Agresso module – “Agresso reports queue”, “Agresso help and temp tables”, “Agresso CON$ system table” (LICENSED)
• MS SQL Server – Management. UNIT4 module for Agresso application. (LICENSED)
• Sybase – job “Dump database”, runs “dump database” command. (BETA)

Bugfix

• Mariadb – job “Framework”. Fix for uninstall Framework job.
• Properties – fix for MariaDB properties “grant_all_privs” and “with_grant_option” when command “show grants for current_user()” returns more than one row.
• Sybase – engine, fix for case sensitive database object names (fails when creating dbw_registerNewParameter procedure)
• Sybase – Management, “on-click” security administration fix.
• Oracle – job “AUDIT TABLE“, improved exception handling.
• DBW – Global report timeout handling
• DBW – Bugfix fdl mult function – preserve whole number
• DBW – Bugfix date rendering in reports
• DBW – Bugfix date ordering in graphs
• DBW – Bugfix jdbc handling in Sybase
• DBW – Bugfix in setting of JDBC driver properties

Improvements

• MS SQL Server – Management. Improved Blocking/Blocked session history views.
• MS SQL Server – job “Backup All transaction logs” collects information for every job execution.
• MS SQL Server – job “MS SQL Server patch status”, new cumulative update for SQL Server 2022 (CU12) and SQL Server 2019 (CU26).
• Sybase – job “Database backup” collects backup statistics into history table and checks if there are any missing statistics in master..monOpenDatabases view.
• DBW – Network stability
• DBW – Database related errors in seperate log file
• DBW – Pie chart – removed decimal if whole number
• DBW – Edit job template – can now delete multiple jobs
• DBW – Edit job template – only one category open at a time
• DBW – Sorting when editing multiple metadata entries
• DBW – Only one Connectivity dialog open at a time
• DBW – Test all button in Connectivity dialog
• DBW – Improved traceroute in connectivity dialog
• DBW – Improved loading speed of management
• DBW – FDL improvement for add/sub – preserve whole numbers

dbWatch Control Center (2024-03-11)

Important note

• Linux release is available as an apt repository, see Linux install guide
• All clients and servers need to be upgraded in a multi-server setup before the connection will resume due to network incompatibilites
• Only the server installation is available on Linux in this release (no graphical client or CCC scripting engine)

New features

• MariaDB – Now supported from version 10.2+. For version 10.1 jdbc driver version 2.7.12 must be used for connection insted of 3.3.3. For MariaDB 5.5 only monitoring without local database is supported.
• MariaDB – “SQL statistics” job, collects detailed information about SQL statements executed on the instance. Supported versions: 10.1+. (LICENSED)
• MariaDB – Management – SQL Performance views showing statistics gathered by “SQL statistics” job (LICENSED).
• MariaDB – Monitoring of Galera Cluster; Node state, Node count, Replica queues, Network staistics.
• Oracle/MS SQL Server – New global report template “Uptime statistics”.
• MySQL/MariaDB – New global report template “Health check report”

Bugfix

• DBW – global report download unstability issue
• Oracle – Management. Improved handling of PDB and CDB instances so that statistics are not mixed between them.
• MS SQL Server – “Health state” job, fix when using CS tempdb.
• MS SQL Server – “Autogrowth settings” job. In an earlier version of dbWatch, the job was initially named “Autogrow settings”, but it was subsequently renamed to “Autogrowth settings”. This change has unfortunately led to the confusion and errors.
• MySQL – Engine. Fixed error when upgrading jobs, and fix for jobs with status which appers without status (new framework versjon 1.32).
• MS SQL Server – “MS SQL Server patch status” job, fix for showing wrong cumulative updates version for SQL Server 2019 (CU23/CU24). Last patch for 2019 CU25 5th apr. 2024
• DBW – Fdl now handles escaping in quoted text.

Improvements

• MS SQL Server – “Update index statistics” job. 2 new parameters that make it possible to store statistics per database.
• MS SQL Server – “DBCC CHECKDB“ job. Improved local report. If “max elap time” is exceeded during execution of the procedure, the report will contain statistics from previous executions until the last database has been checked.
• MS SQL Server – “Reorganize indexes” job. Improved local report. If “max elap time” is exceeded during execution of the procedure, the report will contain statistics from previous executions until the last database has been checked.
• Oracle – Management. Improved “kill session” menu, so that the session executing “alter system kill session” command does not try to terminate itself.
• MS SQL Server – “Database status” job. Collects statistics for periods where the state of the databases has been different from ONLINE. Two new parameters enable ignoring of databases in a none ONLINE state for a long period of time.
• MS SQL Server – Management. New menu in “Files information” table, showing Drive information (size, free space, used space).
• MySQL – “Maximum connections alert” job. Better feedback when the value of max_connections is not available.
• MS SQL Server – “Backup All databases” job. Two new parameters enable compression and creation of subdirectories for each database.
• MS SQL Server – “Backup All transaction logs” job. Two new parameters enable compression and creation of subdirectories for each database.
• DBW – new framework procedure/function for all database platforms (dbw_registerNewParameter). New framework job for upgrading old installations.
• MS SQL Server – Management. Menu “Create new backup device” automatically creates a file name for the device.
• MySQL – “Network statistics” job, fix for avarage statistics calculation.
• Sybase – “Transaction log space check” job, fix for arithmetic overflow.
• MS SQL Server – “Blocking statistics” job, collects hostname for blocked and blocking sessions.
• MS SQL Serer – Management. Added an new column (hostname) to “Blocked/Blocking sessions history” views (job “Blocking statistics” must be upgraded to version 1.9).
• MS SQL Server – “Database backup” job. New parameter “exclude standby databases”, if set to YES the alert will exclude all databases in state online as read-only, with restore log allowed (IsInStandBy property set to TRUE).
• MS SQL Server – “Database Log backup” job. New parameter “exclude standby databases”, if set to YES the alert will exclude all databases in state online as read-only, with restore log allowed (IsInStandBy property set to TRUE).
• DBW – Network stability
• DBW – Improved coloring of area graphs in management

dbWatch Control Center (2024-01-18)

Important note

• Linux release is now available as an apt repository, see Linux install guide
• All clients and servers need to be upgraded in a multi-server setup before the connection will resume due to new node-to-node communication with TLS if you are running the 2023-09-27 release or older
• Only the server installation is available on Linux in this release (no graphical client or CCC scripting engine)

Bugfix

• Rare connection issue (unable to connect) between some clients and servers dependent on TLS configuration settings on one of the hosts. The issue is known and the fix is being tested. A new release with this fixed is due out shortly.

dbWatch Control Center (2024-01-12)

Important note

• Linux release is now available as an apt repository, see Linux install guide
• All clients and servers need to be upgraded in a multi-server setup before the connection will resume due to new node-to-node communication with TLS
• Only the server installation is available on Linux in this release (no graphical client or CCC scripting engine)

Known issues

• Rare connection issue (unable to connect) between some clients and servers dependent on TLS configuration settings on one of the hosts. The issue is known and the fix is being tested. A new release with this fixed is due out shortly.

New features

• DBW – Node-to-node communication now TLS
• DBW – 2 Factor authentication
• DBW – Forced wait time when login fails
• DBW – Clock skew detection and alerting
• DBW – Secure Cloud Router
• DBW – Metadata on jobs
• DBW – Div minor security improvements
• DBW – Optional anonymous access to web pages
• MS SQL Server – “Security and Compliance” module, contains a set of 40 jobs, a report, and a set of Management views for maintaining security and compliance standards (licensed).
• MS SQL Server – New job “Database compatibility” checks if databases run under lower compatibility mode than the SQL Server instance.
• MS SQL Server – New job “Table size collector” – collects table (HEAP and CLUSTER type) size statistics.
• Oracle – New management view “Space usage history” under Storage statistics
• MS SQL Server – New Management view “Object size history” under “database”/Disk and Memory usage/Largest tables/indexes (top 100)/

Bugfix

• DBW – Email extension – no engine job issue
• DBW – Delete dictionary topics
• DBW – Management pie chart issue
• Oracle – Engine for Oracle 8i, error when creating local job reports for instance centric jobs.
• Oracle – Job “Session load”, fix for aggregated statistics for max. and avg. sessions.
• Oracle – Job “Framework” for Oracle 8i, fix error ORA-1400 for jobs with status warning/alarm
• MS SQL Server – Job “Update index statistics”, the procedure now continues to analyze indexes on the next execution if “max elap time” is reached.

Improvements

• DBW – Network message forwarding optimization
• DBW – Div GUI improvements
• DBW – SQL result network handling
• DBW – Report table cell OK marking
• DBW – Report chapter text
• MS SQL Server – Job “AG synchronization lag”. Checks AG synchronization lag time.
• MS SQL Server – Job “Query Store status”, new parameter which enables it to react when Query Store stops.
• MS SQL Server – Job “Objects size collector (all databases)”, new parameter “max objects per graph”, improves visualization of object growth rates in graphs, and new parameter “ignore READ ONLY databases” which enables possibility to ingnore read-only databases.
• MS SQL Server – Job “SQL statistics” increased the max-size value of the database files of the dbwatch database
• MS SQL Server – Job “SQL Server Agent status” new parameter “return status”. Return status value (ALARM – 2, WARNING – 1, or OK – 0) when SQL Server Agent is not running.
• MS SQL Server – Management, improved blockig statistics views.
• MS SQL Server – Job “Blocking statistics”, historical tables include SID values for blocked and blocking sessions.
• MS SQL Server – Job “SQL Statistics”, improved cleanup routine for sql similarity statistics.

dbWatch Control Center (2023-09-27)

Important note

• Linux release is now available as an apt repository, see Linux install guide
• Only the server installation is available on Linux in this release (no graphical client or CCC scripting engine)

New features

• DBW – Support for MongoDB (beta)
• DBW – Alert forwarding pause
• DBW – Support for Global Report FDL merge
• DBW – Network layout view (beta)
• DBW – Management charts now have an optional description field
• DBW – Local report can now access task parameters
• DBW – Added FDL difference function
• MS SQL Server – New job “Session statistics”. Collects detailed information about sessions connected to the instance (part of performance module, licensed)
• DBW – Semi-automatic upgrade for dbWatch Server

Improvements

• Oracle – “SQL statistics” job, fix for missing statistics when counters are reset.
• Oracle – Improved blocking sessions view in Management
• MS SQL Server – New blocking sessions view statistics in Management
• MS SQL Server – Job “Backup All transaction logs” supports Case Sensitive instances and parameter “ignore databases” allows spaces when listing database names
• MS SQL Server – Job “Backup All databases” supports Case Sensitive instances, and better exception handling, and parameter “ignore databases” allows spaces when listing database names
• MS SQL Server – Job “Database backup”, new parameter “exclude log shipping databases”
• MS SQL Server – Job “Database Log backup”, new parameter “exclude log shipping databases”
• MS SQL Server – Job “DBCC CHECKDB“, new parameter “return status when exception”
• DBW – Job “Instance restart alert”, better exception handling
• Oracle – Installation – Fix for missing “select any table” privilege for dbwatch database user on Oracle 8i platform.
• DBW – Server down status on click loads connection info
• DBW – Removing a server connection will now close the socket
• DBW – Excludes local specs in the default profile
• DBW – Dynamic title in management views
• DBW – Improved upload resource dialog
• DBW – Domain login select/unselect all
• DBW – Generate report dialog filtered per domain
• DBW – Global report compatibility now fdl
• DBW – Global report SQL compatibility – improved version handling
• DBW – FDL Union handles an unlimited number of sets
• DBW – Better marking of ‘Running’ state for jobs
• DBW – Better Thread handling in javascript execution
• DBW – Category “Unknown” for incompatible jobs
• DBW – Worksheet can show JSON format
• DBW – Engine transfer between instances

Bugfix

• MySQL – Job “SQL Statistics” – error when installing on InnoDB HA-Cluster (fix in version 1.4)
• MySQL – Job “Query cache hitrate” – error when installing on InnoDB HA-Cluster (fix in version 3.1)
• MS SQL Server – Job “Reorganize indexes in table”, parameter “minimum fragmentation” works now
• MS SQL Server – Job “Data cache memory usage”, missing parameter “memory threshold”
• Oracle – Job “Index status check” for Oracle 8i wrong column name when compiling
• Oracle – Job “Disk read statistics” for Oracle 8i to_char compiling error fix* Avoid multiple domain initializations
• DBW – Monitor hang bug
• DBW – Mail format loading
• DBW – Mail multiple ‘lost connection’ messages
• DBW – Access control for web
• DBW – SQL Worksheet – missing results
• DBW – No engine job properties caching issue
• DBW – Report font resolution fix
• DBW – FDL compare number and text fix.

dbWatch Control Center (2023-06-27)

Important note

This release upgrades encryption standards to AES/GCM 256-bit and from Oracle JDK to OpenJDK.
When upgrading from a previous release in a multi-server environment or environments where the dbWatch Server and dbWatch Client is on different machines, all dbWatch Servers and Clients must be upgraded before you can connect again.
If you encounter any issues, please get in touch with support@dbwatch.com, and we will sort it out for you.

Bugfix

• DBW – Fix for socket handling of outgoing connections from the server
• DBW – Test connections from “Node connections” dialog.
• DBW – Edit access points from Domain Login dialog.
• DBW – Delete role/security group
• DBW – Local report hang/slow bug
• DBW – Missing styling in “Show report” from task editor
• DBW – Fixed issue when transferring domain
• DBW – Save as new report did not work correctly
• DBW – Generate report, select instance did not always populate
• DBW – Upload resource, select file dialog did not always appear
• DBW – Lost connection message could be sent multiple times
• DBW/PostgreSQL – Session to multiple databases issue
• Oracle – “RMAN backup status” jobs, exception pos 0. Added new parameter and the backup history table.
• DBW – Farm views – waits statistics pie-charts

New features

• DBW – “Hover” on table text and date cells.
• DBW – Instance access control from web dashboard.
• DBW – Privileges on dbWatch Servers.
• DBW – Restart Server functionallity
• DBW – Domain discovery on/off setting
• Oracle – new job “Applied archive log gap status”
• MS SQL Server – Management – Sessions Performance views showing statistics gathered by the “Session statistics” job (LICENSED).
• DBW – new internal view for session statistics
• DBW – new job “Connection alert” – check connection status for property and engine users.
• Oracle – new job “Flash recovery space usage” for Standby instances.
• MS SQL Server – new job “Test alert” – Useful for testing extensions (not intended for use in production environments).

Improvements

• DBW – Switched to OpenJDK
• DBW – Switched to bouncycastle for crypto
• DBW – Email extension queue and retry
• DBW – License expired dialog contains the server name
• DBW – Job parameter description trimmed.
• DBW – Certificate CN contains the username
• DBW – AD config copied when transferring domain.
• DBW – Improved message crypto (AES/GCM 256-bit)
• DBW – Lost connection email contains more info
• DBW – Can not delete domain controller node
• DBW – Node info dialog
• DBW – Improved error handling in charts
• DBW – Group configuration now available for Super DBA role
• DBW – Notifications dialog
• Oracle – Default max tablespace size now 20GB
• MS SQL Server – Default max database size now 20GB
• PostgreSQL – “Session load” – parameter replacement to percentage. New session aggregation table.
• Oracle – “Job Scheduling Check” – improved execution time of the job.
• Oracle – Management – improved blocking statistics views.
• MS SQL Server – “SQL Statistics” – improved deletion of old data so that the transaction log to the dbWatch database does not become full.
• MS SQL Server (v. 2014 +) – “Database Log backup” and “Database backup”, new parameter: “exclude databases in Always On availability groups”
• MS SQL Server – “AlwaysOn database backup alert” – 4 new parameters, added differential backup check option and uppercase option.
• MS SQL Server – “AlwaysOn transaction log backup” – new parameter – use_uppercase
• MS SQL Server – “AlwaysOn differential database backup” – new parameter – use_uppercase
• MS SQL Server – “Database Server uptime” – improve resource consumption
• MS SQL Server – “Internal fragmentation check” – new parameter “continue on next run”, makes it possible to carry out the job over several days
• MS SQL Server – “External fragmentation (all databases)” – new parameter “continue on next run”, makes it possible to carry out the job over several days
• MS SQL Server – “Data cache memory usage” – collects execution statistics, new parameter disabling running on instances with high memory usage.

dbWatch Control Center (2023-04-27)

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.
• A problem may occur when installing “RMAN backup status” job on Oracle. Typical error: (Exception, ORA-01403). If this is experienced, please get in touch with support for a patch.

New features

• DBW – Added password policy
• DBW – Job templates can now include other templates in priority order
• DBW – Added ‘Resume monitoring’ menu to instances
• Oracle – new job ‘Tablespace in BEGIN BACKUP mode’ – checks if any data files are in BEGIN BACKUP mode.
• MS SQL Server – ‘MS SQL Server patch status’ – added patches up to 21st Apr. 2023
• MS SQL Server – Management, new menu ‘Create snapshot’
• DBW – New Internal FDL Performance view
• DBW – New Internal sessions view

Improvements

• DBW – Improved feedback in test connection for Email extension
• DBW – Better handling of clock skew in certificate validation
• DBW – Job template editor shows parameter description
• DBW – Improvements to session handling
• DBW – More stable connection for Azure
• DBW – Deleting a job template that is in use is no longer allowed
• DBW – Added threshold for thread dump on high cpu usage
• DBW – Improved styling of errors in tables
• DBW – Performance improvements in property loading
• DBW – Improved ‘Lost connection error’ dialog
• DBW – CSV import now creates subgroups
• DBW – Thread optimization for running engine jobs
• DBW – Added popup when hovering on large table cells
• DBW – Changed firewall settings are enforced at once
• DBW – Added ‘single’ hashtag for forcing single-line fdl result
• MS SQL Server – job “High activity monitor” description change for 4 parameters.
• MS SQL Server – job “Rebuild indexes” has new parameter “ignore tables”
• MS SQL Server – job “Database status” new parameter “ignore standby databases”
• MS SQL Server – job “AlwaysOn transaction log backup alert” improved performance on large AlwaysOn clusters (many nodes)
• MS SQL Server – job “AlwaysOn differential database backup alert” improved performance on large AlwaysOn clusters (many nodes)
• MS SQL Server – job “AlwaysOn database backup alert” improved performance on large AlwaysOn clusters (many nodes)
• Oracle – job “Tablespace free space check” better description if too many tablespaces are in warning/alarm state.
• Oracle – job “Job scheduling check” better exception handling and support for % (percent sign) to represent wild card characters for parameter “ignore job names”
• Oracle – job “RMAN backup status” new parameters and now checks incremental level 0 backup.
• Oracle – job “RMAN archivelog backup status” new parameter.

Bugfix

• DBW – Scheduled report instance list showed guid
• DBW – Delete scheduled report
• DBW – EMail issues for lost connection on no engine instances
• DBW – Jump issue when deleting job in Job template editor
• DBW – Fixed ‘back’ button when creating global report.
• DBW – More stable expanding of nodes in Management
• DBW – Issues with ‘pause monitoring’ for no engine instances
• DBW – Rounding error in fdl div function
• DBW – Issues with setting job template in CSV import
• DBW – ‘Pause monitoring’ was always 30 minutes
• DBW – Buggy adding of metadata in the instance configuration view
• DBW – Buggy ‘Edit dictionary’ dialog
• DBW – Loading of worksheet authentications in multi-server environments
• Oracle – Job ‘SQL statements (Logical reads)’ – better exception handling
• Oracle – Removed RMAN backup jobs for PDB databases
• Oracle – Management fix for Session view for CDB and PDB instances
• Oracle – Job “SQL statistics” – CDB instances do not collect statistics for PDB instances
• MS SQL Server – Management menu fix ‘Change compatibility level’ for 2022
• All DBMS platforms – job “Instance restart alert” better exception handling

dbWatch Control Center (2023-03-10)

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.

Bugfix

• DBW – Job templates could sometimes drop dbwatch monitoring objects in the database
• DBW – Instance status was not always updated when uninstalling a job
• DBW – Table filter did not always work
• DBW – Delete last metadata fix
• Oracle – Handling of Service name
• MySQL – Global report handling

New features

• MS SQL Server – New job “Agent error log”, Checks for errors in the Agent error log

Improvements

• DBW – Improvements to Job Template GUI
• DBW – Job template deployment more robust
• DBW – Job template copy to Server functionality
• DBW – One time monitoring pause
• DBW – Job deployment messages in a separate log file
• DBW – Improvements to edit metadata GUI
• DBW – Add/remove monitoring database
• DBW – Uninstall job with no installation script
• DBW – Message performance improvement in multi-server, single-domain setups
• DBW – Auditing of domain config changes
• MS SQL Server – New version of “Query Store status” (1.2) job, fix for history data
• MySQL – New version of the “MySQL max connections” (1.2) job, does not change status to OK after WARNING/ALARM (error when using Max_used_connections value)
• MS SQL Server – New version of “MS SQL Server patch status” (1.9), added patches up to 16th Feb. 2023
• MS SQL Server – New version if “High activity monitor” (1.8) job – fix for NULL details when “Page lookups/sec” counter is missing
• Oracle – fix in the local report for “CPU load check” Oracle.

dbWatch Control Center (2023-02-10)

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.

Bugfix

• DBW – Rename instance
• DBW – Access control fix for “Edit connections” in Domain Configuration
• DBW – Refresh bug in “Jobs Status” in Monitoring View
• DBW – Fix for Delete Job Template
• DBW – Escape handling in Job Template config file
• Oracle – Feedback in Worksheet for buggy SQL statements
• MS SQL Server – New version of “High activity monitor” (1.7), Divide by zero error fix
• MS SQL Server – New version of “Objects size collector (all databases)” (1.5), “04 Incorrect syntax near the keyword” fix.
• MS SQL Server – New version of “Transaction log space usage” (2.3), bug fix for invalid usage of DECLARE CURSOR statement
• MySQL – property fix for memory_usage, disk_usage and edition

Improvements

• DBW – Job template mode has been renamed for better readability
• DBW – Improved safeguards when enforcing Job Templates
• DBW – Timeout in SQL Worksheet

dbWatch Control Center (2023-02-07)

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.

New features

• DBW – Job Template Editor
• MySQL – New performance tuning module (this functionality is licensed)
• MySQL – New job “SQL statistics.” Collects statistics for the “SQL performance module” available in Management GUI (this functionality is licensed)
• DBW – License Management View
• DBW – Audit of user actions

Bugfix

• DBW – Fix for polling pause edit
• DBW – Email extension Reconnected message
• DBW – Fix for incorrect TLS handling in email extension
• DBW – Custom tabs in the Monitoring view
• DBW – Handling of duplicate properties when using local definitions
• DBW – Task editor slow issue
• DBW – Minor stuff
• MS SQL Server – Set management auth forgot the database
• Oracle – Support for INTERVALYM / INTERVALS
• MySQL – Fix for job upgrade
• PostgreSQL – Fix for job upgrade
• Azure – Management fix for Azure single db

Improvements

• DBW – New look & feel for Group Configuration
• DBW – More robust CSV import
• DBW – Better logging of adding/removing instances to Server Notes
• DBW – Improved formatting of SMS messages
• DBW – Improvements to Access Control
• DBW – Improved handling of parallel sessions in management
• DBW – Edit Jobs available from the Manage Jobs view
• Oracle – New version of “CPU load” (3.7), new parameter “Time threshold”
• Oracle – New version of “Long running queries” (1.6), fix for lowercase
• MS SQL Server – New version if “SQL statistics” (1.6), new parameters to enable/disable similarity query text calculations.
• MySQL – New job “Network statistics” replaces “Network traffic”
• MySQL – New version if “Query cache hitrate”, now with status, new parameters, and better exception handling
• MySQL – New job “Threads statistics” replaces “Thread cache hitrate”
• MySQL – New job “Statement load” replaces “Database load”
• MySQL – New version of “DBMS uptime”, new parameters, and better exception handling
• MySQL – New version of “Binlog cache check”, new parameters, and better exception handling
• MySQL – New version of “Innodb buffer pool check”, new parameters, and better exception handling
• MySQL – New job “MyISAM key cache check” replaces “Buffer key cache check” and “Key buffer check”
• MySQL – New job “Framework”, for internal use only (added new procedure – dbw_remove_job proc)
• MySQL – New version of “Session load”, better exception handling
• MySQL – New version of “Temporary table check”, new parameters, and better exception handling
• MySQL – Improved resolving of Memory and Edition properties

dbWatch Control Center (2022-12-15)

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.

New feature

• DBW – Firewall
• DBW – Command line interface (CCC)
• DBW – Authentication for Web dashboards
• DBW – Web Dashboard Editor now in beta
• PostgreSQL – New job “Blocking statistics”. Checks for blocked and blocking processes.
• MS SQL Server – New job “Autoshrink settings”. Check if all databases have auto-shrink turned off.
• MS SQL Server – New job “AlwaysOn differential database backup”. Check the backup date (type I, differential backup) for all local databases and databases in the AlwaysOn groups (primary and secondary).
• PostgreSQL – Support for Postgres 15 for «SQL statistics» – Performance module.
• PostgreSQL – New “Blocking view” in Management.
• Linux installer included

Improvement

• DBW – More flexible access control.
• DBW – Improved wizard for adding SQL Cluster.
• DBW – CSV import handles multiple license tags.
• MS SQL Server – New version of “AlwaysOn database backup” job (2.9). Now supports instances on the same host.
• PostgreSQL – New version of “Schema growth and information” job (1.8). Improved synchronization with the “Schema growth collector” job, and better exception handling.
• Oracle – New version of “Long running queries” job (3.5). New parameter “Exclude schemas”.
• MS SQL Server – New version of “Transaction log space usage” job (2.2) for MS SQL Server 2017+. DBCC SQLPERF replaced with sys.dm_db_log_space_usage.
• Oracle – Improved handling of Oracle database link in management.

Bugfix

• DBW – Domain configuration – delete node.
• DBW – CSV import – name collision avoidance for Oracle and MS SQL Server.
• DBW – Instance reconnect issue.
• DBW – Fix for HTML-based global reports.
• DBW – Minor fixes.
• PostgreSQL – New version of “SQL statistics” (1.2) job. Fix for deleting of old statistics.
• PostgreSQL – New version of “Vacuum alert” job (2.7). Spelling mistake.
• Oracle – full version display fix for Oracle 18+.

Known bugs

• Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver.
• Importing instance configuration data from dbWatch Enterprise Manager 12, does not work with Oracle RAC and Dataguard systems

dbWatch Control Center (2022-11-03)

New features

• PostgreSQL – No longer beta. Old engine installations must be reinstalled.
• PostgreSQL – new performance tuning module (this functionality is licensed)
• DBW – AD integration
• DBW – GUI for Web Server initialization
• DBW – Web Dashboard now available

Bugfix

• MS SQL Server – New version (1.1) of the “Query Store status” Job. Handles unavailable databases
• DBW – Bugfix instance reconnect issue
• DBW – Bugfix refresh issue in the Manage Jobs view
• DBW – Bugfix job autoupgrade
• DBW – Bugfix fdl orderby NoValue

Improvement

• MS SQL Server – New version (1.5) of the “SQL statistics” Job. Now handles missing indexes
• DBW – QueryLog view now contains SQL
• DBW – Improved edit node connections dialog
• DBW – Improved handling of misconfigured extensions
• DBW – Improved handling of Job installation failure
• DBW – Improved global report generation

dbWatch Control Center (2022-09-29)

Known issues

• SQL Server Consolidation report is visible in the release but is not working as underlying extra cost features are omitted

New features

• MS SQL Server – new performance tuning module (this functionality is licensed)
• MS SQL Server – new job “Query Store status.” Checks Query Store space usage.
• MS SQL Server – new configuration options for Query Store in Management GUI
• MS SQL Server – new job “SQL statistics.” Collects statistics for the “SQL performance module” available in Management GUI (this functionality is licensed)
• MS SQLServer – Kerberos integration
• Oracle – new job “SQL statistics.” Collects statistics for the “SQL performance module” available in Management GUI (this functionality is licensed)
• Oracle – new performance tuning module (this functionality is licensed)
• MariaDB – Now supported
• PostgreSQL – Support for version 14
• DBW – Management graph range restriction/zoom
• DBW – Management selectors
• DBW – Management tabs
• DBW – Management Studio query plan viewer integration
• DBW – Improved CSV import (JDBC driver & global auth)
• DBW – Logging of instance adding to server notes
• DBW – Domain transfer
• DBW – Feedback when license change will disable jobs
• DBW – Freetext notes
• DBW – Job failure log summary

Improvements

• MS SQL Server – new version 1.7 of “MS SQL Server patch status” --> checks for new patches for MS SQL 2014, 2017, and 2019 released before 2022.09.20.
• Oracle – Performance moved into Server activity in management, making room for a new performance module
• Oracle – Improved Amazon RDS support

Bugfix

• Oracle – Adding data files and changing storage in OMF
• Oracle – Extending and altering tablespaces in RDS
• Oracle – RMAN information didn’t show up correctly in some instances
• Oracle – Instance alert log check, fixed typo in the report
• Oracle – Fixed bug when adding instances with OMF or ASM
• Oracle – Fixed issue on multi-dataguard sites not being possible to add
• Oracle – Multitenant screen in management stuck on loading
• Oracle – Some management screens stuck on loading
• Oracle instance-id handling in management
• PostgreSQL . Postgres 9.6 is not getting detected correctly in the management module
• PostgreSQL – Replication delay sometimes didn’t detect replication
• PostgreSQL – Fixed typo in property, causing some jobs not to show up
• PostgreSQL – BDR replication job installable on non-BDR setups
• PostgreSQL – SSH-based jobs visible without configuring ssh
• MySQL – Fixed many graphs not showing correctly on some versions
• MySQL – Some management screens are stuck on loading
• MySQL – Issue when uninstalling jobs
• Linux – Fixed issue on CPU usage and Disk usage checks not showing up
• SSH connector stability
• DBW – FDL with restricted access to instances
• DBW – ISsues with triggering of no engine jobs
• DBW – Issues with instance property flush
• DBW – Try again when property resolving fails

Note on upgrade
For customers upgrading from previous versions of dbWatch Control Center, be sure to take a backup of the C:\ProgramData\dbWatchControlCenter\config directory. Feel free to contact dbWatch support if you need any assistance. We are happy to help you via zoom or TeamViewer.

Remember that a new “dbWatch Control Center” service is created when you run the installer. If this service has been configured under an account other than the local account, remember to reconfigure it again.

There is also a new license structure. After upgrading, all jobs will execute normally, but installing new jobs and uninstalling already installed jobs may be disabled (depending on your current license). If you experience any issues, contact us, and we will provide you with an updated license.

dbWatch Control Center (2022-05-25)

Bugfix

• DBW – Fix alert triggering with different timezones.
• DBW – Monitor/Server connection issue fix.
• DBW – Fix for lack of automated refresh in management view.
• MS SQL Server – new version 1.3 of “Sessions per database.” Fixed NOT NULL constraint error, improved exception handling
• MS SQL Server – new version 1.2 of “Database growth rate (aggregated).” Fix for arithmetic overflow (error converting expression to data type int) for databases larger than 2.1 TB
• MS SQL Server – new version 1.8 of “Database growth rate (detailed).” Improved exception handling
• MS SQL Server – new version 2.1 of “Transaction log size check.” Fix for arithmetic overflow (error converting expression to data type int) for databases larger than 2.1 TB
• MS SQL Server – new version 1.7 of “Blocking statistics.” Better handling of NULL values in details.

dbWatch Control Center (2022-05-05)

Improvements

• DBW – Added timeout setting for no engine jobs
• DBW – Performance improvements in monitoring for large environments
• DBW – Engine job triggering is more robust
• DBW – No engine jobs use less disk space in the property store
• Oracle – New version 2.8 of “Session load Rac.” Transformed to an alert with eight new parameters (need dbWatch Server restart after upgrade).
• Oracle – New version 3.3 of “Session load.” Transformed to an alert with four new parameters (need dbWatch Server restart after upgrade).
• Oracle – Improved history in session graph
• MS SQL Server – New version 2.2 of “Database disk capacity.” Supports now log list of drive specifications.
• MS SQL Server – New version 1.6 of “MS SQL Server patch status.” Checks for patch CU16 for MS SQL 2019, RTM CU28, and RTM CU29 for MS SQL 2017.
• Postgres – Improved history in session graph, logical reads, and transactions per second
• Oracle – Extent fragmentation job – added parameter for skipping tablespaces
• Oracle – Tablespace free space for noschema installation, now supports excluding tablespaces and including unallocated free space
• Postgres – BDR replication lag, new parameter max histr interval, allowing old historical records to be removed automatically
• MS SQL Server – New version 1.61 of “Check database recovery mode.” Excludes mirrored and Availability Groups databases
• MS SQL Server – New version 1.4 of “Database backup (system databases). Added to new parameter for better configuration flexibility
• MS SQL Server – New version 1.72 of “Index usage statistics.” More trace info when an exception occurs. It also excludes the tempdb database.
• MS SQL Server – New version 2.54 of “DBCC CHECKDB.” Added new parameter “ignore errors” to exclude irrelevant exceptions
• MS SQL Server – New version 1.3 of “Transactions log flushed bytes load.” Better exception handling

New features

• DBW – Added views for insight into dbWatch routing and connection info
• DBW – Instance config in separate files
• DBW – Left side tree in monitor now minimizable
• DBW – Single domain multiserver now in beta
• DBW – Lots of changes to internal views
• DBW – Restart the node network in the server’s context menu.
• DBW – Webserver
• DBW – New vmoptions settings for debug output
• Healthcheck report added for Oracle, Postgres, and MySQL
• Oracle – RMAN archivelog backup job, monitoring archivelog backup sets
• MS SQL Server – New alert 1.1 “Shrink transaction logs” – shrinks tr. logs detected by “Transaction log size check” alert

Bugfix

• DBW – Lots of fixes for general stability
• DBW – Fixed memory leak for no engine jobs
• DBW – Job template handling
• DBW – Lots of fixes for network stability
• DBW – Changes to group defaults sometimes caused the config file to be corrupted
• DBW – Management specification loading more robust
• DBW – Now handles Oracle timestampz type
• DBW – Unregister instance now works
• DBW – License handling when the license is almost depleted
• MySQL – Uninstall job now works on MySQL 6 and newer
• MySQL – Bugfix for performance-related jobs that did not get correct values
• Oracle – Create user menu option moved to correct location
• Postgres – Bugfix in management security view that was not showing
• MySQL – NDB jobs are now not included in the default install
• Oracle – Alert log check, a minor adjustment in the description
• Oracle – RMAN backup job, now ignoring archivelog backup sets
• Oracle – Autoextensible files job improved compatibility query
• Oracle – Extent fragmentation – Improved query for better database response
• Oracle – Top user memory usage – New default threshold values
• MS SQL Server – New version 1.8 of the “framework” task. Engine fix for SQL Server 2000 (database-centric alerts).
• MS SQL Server – New version 1.2 of “Shrink transaction log.” Bug when deleting history records. (CC)
• MS SQL Server – New version 1.7 of “Database growth rate (detailed).” Missing parameter when a new installation
• MS SQL Server – compatibility fix in Management views
• MS SQL Server – cosmetic fix for local report for [Test DML-DDL performance] job
• MS SQL Server – missing [activity_dtu_test] property. Fix of [Performance test] in the Management view

dbWatch Control Center (2022-02-14)

New features

• MS SQL Server – New version (1.4) of “MS SQL patch status.” Checks patch level of SQL Server instance.
• MS SQL Server – New job “Shrink transaction logs.” Shrinks tr. logs detected by “Transaction log size check” alert
• DBW – New fdl topic “iospeed.”

Improvement

• MS SQL Server – New version (1.61) of “Check database recovery mode.” Excludes mirrored and Availability Groups databases.
• MS SQL Server – New version (1.4) of “Database backup (system databases).” Added to new parameter for better configuration flexibility
• MS SQL Server – New version (1.72) of “Index usage statistics.” More trace info for exceptions (excludes tempdb database)
• MS SQL Server – New version (2.54) of “DBCC CHECKDB“. Added new parameter “ignore errors” to exclude irrelevant exceptions
• MS SQL Server – New version (1.3) of “Transactions log flushed bytes load.” Improved exception handling
• DBW – Improved stability in multi Server/multi Client setups
• DBW – New implementation of job triggering.
• DBW – More stable property loading
• DBW – Job templates can be triggered for a single instance
• DBW – Improved network logging functionallity
• DBW – More stable Domain Controller startup

Bugfix

• MS SQL Server – Bugfix in Management database compatibility menu
• Oracle – Fixed bug in management. Results not showing
• Oracle – Disk space check did not displace space correctly on Windows Server 2019
• Oracle – Rebuild indexes report not displaying correctly
• DBW – Bugfix for initial loading of authentications in SQL Worksheet

Some changes to the config file layout. The server will move the files at the first startup. Some users have experienced needing to restart the server again for the changes to have an effect.

dbWatch Control Center (2022-01-14)

Bugfix

• DBW – Bugfix in the handling of property storage policy
• DBW – Removed false, lost connection messages
• DBW – Metadata dictionary can now delete values
• DBW – Buggy license counting fixed
• DBW – Minor stability issues fixed
• MS SQL Server – Bugfix for “External fragmentation (all databases)” job
• MS SQL Server – Bugfix for “[Check database recovery mode” job
• MS SQL Server – Bugfix for “Index usage statistics (all databases)” job
• MS SQL Server – Bugfix for “Filegroups growth rate” job
• Oracle – Bug fix in compatibility tag that made some jobs disappear from the manage jobs overview
• Oracle – Added pre-implementation steps for some scenarios where jobs didn’t install
• Oracle – Typo fixes in multiple reports

New features

• DBW – Job templates – deploy jobs in bulk
• PostgreSQL – Added job BDR Replication lag

Improvements

• DBW – Added metadata dictionary key syntax check
• DBW – Lost connection handling Monitor/Server

Known issues

• Oracle – Job templates do not work correctly on RAC

dbWatch Control Center (2021-12-22)

Bugfix

• Oracle – RMAN 11g Backup check, intermittent exceptions due to lack of privileges
• Oracle – RMAN backup check for 12 and newer, intermittent exceptions due to lack of privileges
• Oracle – Job scheduling check, intermittent exceptions due to lack of privileges
• Oracle – ASM disk statistics check, intermittent exceptions due to lack of privileges
• Oracle – ASM diskgroup check, intermittent exceptions due to lack of privileges
• Oracle – Autoextensible files check, intermittent exceptions due to lack of privileges
• Oracle – Free extents check, intermittent exceptions due to lack of privileges
• Oracle – Tablespace free check, intermittent exceptions due to lack of privileges
• Oracle – Job Scheduling check, improved handling of large job names and multiple errors
• Oracle – Tablespace free space check, improved handling for ignored tablespaces
• Oracle – new version: Delete SYS.AUD$ data
• Postgres -new version: Session load
• DBW – handling of engine scripts with multiple versions
• DBW – Bugfix in task editor – save as new

Improvements

• Oracle – Adjusted history thresholds to a minimum of 14 days for jobs
• Oracle – Improved graphs Management, Better history for Logical IO
• Oracle – Improved graphs Management, Better history for Network throughput
• Oracle – Improved graphs Management, Better history for Transactions per sec
• DBW – sub/add function now has optional timeunit argument
• DBW – improvements to job template handling
• DBW – improvements to monitor/server socket handling
• DBW – improvements to the internal initialization sequence
• DBW – filtering dates in tables
• DBW – improved caching of management specifications on the monitor
• DBW – improved handling of Oracle RAC
• DBW – improved handling of Oracle Dataguard
• DBW – improved handling of service groupings
• DBW – improved handling of exhausted license
• DBW – improved property loading
• DBW – number alignment in tables
• DBW – improved default mail configuration

New features

• MySQL – new job: Innodb cluster status
• MySQL – new job: Innodb cluster switch
• MySQL – new job: Replica count
• MySQL – new Job: Replica delay
• MySQL – new Job: Replica state
• MySQL – New job for NDB cluster, NDB data node status
• MySQL – New job for NDB cluster, NDB data memory usage
• MS SQL Server – added Kerberos support
• MS SQL Server – new task: Database session load
• MS SQL Server – new version: Database growth rate detailed
• MS SQL Server – new version: Database disc capacity
• MS SQL Server – new version: Filegroups growth rate
• Oracle – Adding ssh based jobs for AIX and Linux
• DBW- task parameter default value now available in fdl
• DBW – instance import now supports job templates
• DBW – added instance menu to status tables
• DBW – added ssh support
• DBW – added compacting of static property store

dbWatch Control Center (2021-10-19)

New features

• Basic job template support
• Added new Farm Maintenance views for Microsoft ERROR log statistics
• New job for MS SQLServer, “Database session load,” which collects session statistics per database

Bugfix

• Pie chart color rendering
• Fixed issues in PostgreSQL reconnect

Improvements

• Improved speed for Oracle connect
• More robust socket handling
• Cosmetic changes to the Domain Login dialog
• Server performance improvements
• Improved Internal views

Misc

• Removed backup statistics from Farm views

dbWatch Control Center (2021-09-09)

• Improvements to domain handling
• Improvements to network stability
• Improvements to FDL handling in multi-domain setups
• Improvements to eval license handling

• New dialog for initial domain setup
• New Login Dialog
• New E-Mail configuration dialog

• Added ‘Clone & Detach’ feature for charts and tables

• Bugfix: for Copy Cell
• Bugfix: You can now uninstall upgradable no-engine jobs
• Bugfix: Local reports for no engine jobs
• Bugfix: Missing labels on some charts
• Bugfix: Configuration backups
• Bugfix: Countless minor bugfixes

• New version of MS SQLServer “Agent Jobs Check” 2.7
• New version of MS SQLServer “framework” 2.2
• New version of MS SQLServer “Database disk capacity” 2.0
• New version of MS SQLServer “Wait statistics” 1.6
• Backup overview (for MS SQL Server) – Beta
• Maintenance overview (for MS SQL Server) – Beta

• Oracle Dataguard apply time, a new basic report added
• Oracle Dataguard archive sequence apply lag, a new basic report added
• Oracle Dataguard gap alert, a new basic report added
• Oracle Dataguard startup time, a new basic report added
• Oracle Dataguard transport time, a new basic report added
• Oracle Dataguard apply time, adjusted default schedule to run less frequent
• Oracle Dataguard archive sequence apply lag, adjusted default schedule to run less frequent
• Oracle Dataguard startup time, adjusted default schedule to run less frequent
• Oracle Dataguard transport time, adjusted default schedule to run less frequent
• Oracle Dataguard datafile status, adjusted default schedule to run less frequent
• MySQL/MariaDB, Improvements in engine scripts for improved cloud support
• Oracle DB Uptime, Fixes for report issues
• Postgres Locks held and statistics, Bugfix on job reinstall issues
• Postgres Transaction statistics, Bugfix on job reinstall issues

dbWatch Control Center (2021-05-28)

Bugfixes

• Metadata storage fixed
• Improved stability in message routing
• Incorrect refresh in the Manage Jobs view
• Version handling when importing no-engine jobs
• Missing label in report charts
• Adding instances with MySQL 5.0 – 5.6 on AWS or on-premise could fail with privilege issues
• Oracle database network statistics improved housekeeping
• Server selection now works in the Extension view

Improvements

• Support for AlwaysOn cluster
• Added time topic for server
• Improved “Domain Login” dialog
• Improved “Connected users” view
• New “Internal Notes” views
• New “Internal engine files” views (MS SQL Server, Oracle)
• Can now “delete” auto-discovered instances

Known issues

• AlwaysOn
  • You can get an error the first time you execute the “AlwaysOn database backup alert” and “AlwaysOn transaction log backup alert.”
  • The databases in Availability groups are not shown in management.
  • You must select “Cluster” as a grouping in the tree. This selection is forgotten on Monitor restart.

dbWatch Control Center (2021-05-06)

Bugfixes:

• Connection stability issues monitor/server
• Issues with job upgrade
• Issues in add instance wizard
• Issues in Connect/Disconnect to all instances
• Duplicates in upload resource view
• Sort order in the acknowledgment history view
• Fixed “Show error log,” for instance
• Stability issues in chat
• Lots of minor fixes in stability and user interface

Improvements

• Improved dialog for initial domain setup
• Improved installation wizard
• Added “busy” indicator in domain login dialogs
• Login on entering in domain login
• New version for MS SQL Server “Database growth rate (detailed)” job
• New version for MS SQL Server “Filegroups growth rate” job
• New version for MS SQL Server “Transaction log space usage” job
• New version for MS SQL Server “Database disk capacity” job

dbWatch Control Center (2021-04-23)

Improvements

• More user-friendly flow for initial installation
• Improved stability
• Improved Access control

Bugfix

• Generation of global reports

Limitations

• Multi-domain is not stable
• Postgres drivers can only support up to version 9.6 since the available driver only applies to 9.2.1003, which does not have SCRAM-SHA-256.
• dbWatch server on Linux and Ubuntu are not yet supported
• Same MySQL installation error as RC 3
• PostgreSQL unstable (Work in progress)

dbWatch Control Center RC 4.0

RC 4.0 focuses on UI stability and additional features from RC 3.0

New Features

• Recommended to install to a small environment with instances no more than 100 instances
• Upon installation, dbWatch will ask for the license file
• SMTP extensions for emails
• UI stability where the connection does not prematurely die
• Brent Ozar module.
• Farm Module Views are split into three separate files; this is a fix to RC3‘s single instance view problems when there are more than 20 instances registered

Known Issues:

• Postgres drivers can only support up to version 9.6 since the available driver only applies to 9.2.1003, which does not have SCRAM-SHA-256.
• dbWatch server on Linux and Ubuntu are not yet supported
• Same MySQL installation error as RC 3
• Recovery options for MSSQL are only limited to SIMPLE recovery (FULL backup restore)
• In the “Add Instance” Wizard, UI locks the “NEXT“ button when returning from the job installation process
• Limited Security Set-up – only admin credentials are available with six instances
• Bulk Installation is still riddled with bugs when installing databases

dbWatch Control Center RC 3.0

RC 3.0 integrates a few new features from RC 2.0

New Features

• Can support up to 100 databases for now; will keep on expanding to accommodate more
• Autodiscover feature
• dbWatch internal is added as a view

Known Issues:

• Connection dies after 30 minutes of no activity
• MySQL installation for version 8 and above encounters an error during installation
• dbWatch server on Linux and Ubuntu are not yet supported
• More than 20 instances will cause a bug for single instance views; you can still see the overview but clicking on an instance will
• No stress testing is done with multiple servers housing hundreds of databases
• In the “Add Instance” Wizard, UI locks the “NEXT“ button when returning from the job installation process
• Limited Security Set-up – only admin credentials are available with six instances at max
• Bulk Installation is still riddled with bugs when installing databases

dbWatch Control Center RC 2.0

RC 2.0 is an improvement from RC 1.0 regarding UI stability and dbWatch server connection.

New Features

• Can support up to 100 databases for now; will keep on expanding to accommodate more
• Bulk Instance Installation
• Supports up to Postgres 12 and MySQL database engines

Known Issues:

• No comprehensive testing done with Sybase, MySQL, MariaDB, Ingres and Postgres
• dbWatch server on Linux not yet supported
• No stress testing is done with multiple servers housing hundreds of databases
• In the “Add Instance” Wizard, UI locks the “NEXT“ button when returning from the job installation process
• Limited Security Set-up – only admin credentials are available with six instances at max
• Bulk Installation is still riddled with bugs when installing databases

dbWatch Control Center RC 1.0

Control Center takes your monitoring solutions to new heights. Similar to dbWatch 12.7, it covers all your monitoring needs.
More importantly, it builds on its functionality and user-friendly design with the following:

• Extensive dashboards and view to monitor and manage larger database server farms
• new and easy-to-use UI
• Expand the job list of dbWatch 12.7 monitoring solution for SQL and Oracle even further
• Supports Oracle 12, 18 and 19, and MSSQL 2012, 2014, 2017 (Mysql)
• Farm Data Language – an improved version of Dbwql

Tested and supported:

• Oracle 8, 9, 10, 11, 12, and 9; both standard and enterprise editions
• MSSQL for 2000, 2005, 2008, 2012, 2016, 2017, and 2019; both for Standard and Enterprise Editions
• dbWatch Server installed on Windows 10

Known Issues:

• No full testing done with Sybase, MySQL, MariaDB, Ingres and Postgres
• dbWatch server on Linux not yet supported
• Incoherent error detection, such as character limit that prompts error: illegal characters inputted
• No Max and Min hours of scheduling.
• Repeated configuration in installing jobs can produce bugs
• No stress testing done with multiple servers housing hundreds of databases
• In the “Add Instance” Wizard, UI locks the “NEXT“ button when returning from the job installation process
• Limited Security setup – only admin credentials are available
• Stability Issues when connecting to several servers