CloudDM 4.8.0 adds GreptimeDB as a DataSource
Skip to main content

CloudDM 4.1.2

  • Release date: August 26, 2026
  • Version: 4.1.2

Highlights​

  • SQL tickets now analyze DML impact and execution plans across multiple database engines and can resume interrupted analysis.
  • SQL engines use the database version and session settings for parsing, statement splitting, behavior analysis, rules, lineage, and rewriting.
  • Search tickets by description or inline SQL, rename downloaded results, and audit exports and downloads.
  • Oracle supports a configurable client character set. ClickHouse adds support for more complex types and improves connection compatibility.

Added​

  • SQL tickets estimate affected rows and analyze plans for MySQL, TiDB, Doris, Dameng, PostgreSQL, SAP HANA, SQL Server, Oracle, StarRocks, Db2, MariaDB, and ClickHouse. Analysis reports progress, skipped statements and errors, and supports lease recovery and concurrent isolation. (#260)
  • Administrators can declare a default driver version in drivers.xml. The DataSource creation form selects that version by default. (#260)
  • You can name a result file before downloading it. Empty names and invalid characters are rejected. (#299)
  • Operation audit captures result exports and downloads with file and operation details, and displays resource fields more clearly. (#302)
  • The ticket list supports partial matching on descriptions and inline SQL and lets users copy ticket descriptions. (#305)
  • Oracle connections can specify a common or custom client character set for decoding CHAR and VARCHAR2 values. (#295)

Improved​

  • SQL analysis uses the actual server version and session settings such as sql_mode for parsing, completion, splitting, permissions, lineage, and rewriting. It also improves MySQL version support, Dameng security domains, and Doris and StarRocks table metadata. (#260)
  • Ticket details bring impact estimates, objects, behaviors, analysis errors, and execution progress together. Large SQL previews and task recovery are more stable. (#260)
  • Improved localization and layout for DataSource settings, security-rule details, SQL logs, and environments. Ticket controls and scheduler logs follow the user's language. (#300, #304)

Fixed​

  • Standalone Docker now restores embedded MySQL accounts from persisted configuration when recreating a container, creating missing users or synchronizing passwords as needed. Thanks to @sunjiajie. (#272)
  • ClickHouse handles fetchSize correctly and can read JSON, Map, Tuple, Dynamic, Variant, and nested Array values. Thanks to @BetaCat0. (#253)
  • Fixed a type conversion error in lineage and security-rule analysis when SQL function arguments include non-SELECT scopes. Thanks to @sunjiajie. (#259)
  • Synchronous OpenAPI queries return errors and warnings that are not displayed in the Console, without collecting the same message twice. Thanks to @sunjiajie. (#281)
  • Fixed duplicate plan wrappers, EXPLAIN classification, older ClickHouse connections, Db2 for z/OS time zone parameters, and SQL Server SHOWPLAN compatibility. (#260)
  • Fixed analysis of ClickHouse EXISTS subqueries, Oracle multi-row INSERT ... VALUES, and PostgreSQL INSERT ... SELECT. Improved INSERT row estimates across databases. (#260)