Tonic Structural release notes

v610 - v618
v610 - v618
Removed
October 28, 2022

Enhancements

The Subsetting view now shows for each table the percentage of data that is included in the destination database.

Other updates

The workspaces view no longer briefly flashes a message indicating that the workspace cannot be found.

Added the ability to display trace information in the log files. To enable the trace information, set the environment variable TONIC_LOG_TRACES to true.

Fixed an issue that caused an incorrect warning to display when linking columns that were assigned the Custom Categorical generator.

Fixed a data type error in AI Synthesizer for models that only contain categorical data.For the Event Timestamps generator, Tonic now prevents the generator from being assigned to a time-only value.

Amazon Redshift

  • Added ServerCompatibilityMode to the Redshift connection string to prevent connection errors.

Databricks

  • Added support for Databricks 10.x.

MongoDB

  • Fixed an issue where Tonic generated collection names in Preserve Destination mode that exceeded the maximum length limit.

MySQL

  • The MySQL data connector now supports the ability to use the DELIMITER command in post-job scripts.

Oracle

  • Improved performance for schema queries.
  • Improved performance for databases without database links.
  • Restored missing information for loader errors.
  • Improved performance for applying indexes and constraints.
  • Added the environment variable TONIC_ORACLE_REDO_LOG_ENABLED, which by default disables recovery information writes to REDO LOG files.
  • Improved performance for retrieving tables and columns.
  • Fixed an issue with loading custom types.
  • Fixed an issue where multiple indexes on the same column caused data generation to fail.
  • Corrects a regression from V611.
  • When fetching constraints, Tonic can now support primary key indexes that have the same name.
  • Excluded views from table queries.

PostgreSQL

  • Updated the process of loading tables to improve performance and eliminate an error indicating that PostgreSQL types could not be found.

SQL Server

  • Fixed an issue where Preserve Destination and Incremental table mode could not be used in tables with foreign key relationships.
  • Tonic now provides a more informative error when data generation fails because the database is not accessible.
  • Tonic now properly handles identifiers with single quotes.
  • Fixed an issue that caused a worker process to crash when using Azure to connect to the database.
  • Added additional logging of the available databases.
  • Improved handling of schema and table names in privacy scans.