Tonic Structural release information

To ensure uniqueness, the names of replacements created in Collection View or Document View now incorporate the data type.

PostgreSQL - Improved the performance of loading workspaces and testing database connections.

New Document View option to configure file connector JSON columns - For JSON file connector columns, instead of the JSON Mask generator, you can use the new Document View option to view the JSON structure and to assign generators to each combination of path and data type within the JSON. On the column configuration panel for a file connector JSON column, toggle Use Document View to the on position. Document View displays as a new tab on the workspace management view.

On the recommended generator panel for columns, fixed an issue where the preview data was not generated.

SQL Server - The TONIC_SQL_SERVER_SCRIPT_NO_FILE_GROUPS configuration setting is now respected when creating constraints in the destination database.

SQL Server - Improved column length mismatch handling for SQL Server bulk copy.

File connector - For a workspace that uses a file mount as a file source, you can now write the output files to Google Cloud Storage.

Oracle - Fixed an issue with the creation of synonyms that reference objects in other schemas.

File connector - On self-hosted instances, you can now configure a file mount as the source for file connector workspace files. After you set up the file mount, to enable the file mount option, you configure the file mount path as the value of the environment setting TONIC_FILE_MOUNT_POINT. For a file mount workspace, you can write the output to Amazon S3 or back to the file mount. Similar to cloud storage workspaces, you can select files or folders, and filter the file types to include.

SQL Server - Structural now skips creating Plan Guides that have null characters in their names.

SQL Server - Fixed an issue that caused data generation on Tonic Structural Cloud to fail when Tonic Ephemeral Cloud was the output location.

Bug fixes and other internal updates.

Bug fixes and other internal updates.

Database View now uses the full width of the browser.

Bug fixes and other internal updates.

SQL Server - Added additional enhancements and a new configuration setting to more gracefully handle null characters in object names.

MongoDB - Enabled the Timestamp Shift generator.

MySQL - In MySQL workspaces, you can now provide custom names for the destination schemas. Note that if you create the database schema yourself, you cannot rename the destination schemas.

Bug fixes and other internal updates.

MySQL - Resolved an issue that occasionally caused errors when getting the schema scan history.

PostgreSQL - Improved the performance of connection tests for large databases.

Bug fixes and other internal updates.

Databricks - Fixed an issue with the Test Cluster Connection option on the workspace settings page where the provided databases were not respected.

PostgreSQL - Fixed a regression, which was introduced in v1391, in the handling of Range types.

Fixed an issue that caused the Timestamp Shift Generator to output strings in a different date format.

PostgreSQL - Fixed a regression in v1391 where Postgis extension types were not processed properly.

Oracle - Enhanced performance and memory usage while working with Oracle CLOB data.

Databricks - For a Databricks workspace, you can now specify a list of source schemas to include. When you specify multiple source schemas, Structural automatically creates the same schemas in the destination database.

Databricks - Fixed issues to allow Databricks workspaces to function when the user does not have access to all of the tables in the source schema.

Bug fixes and other internal updates.

SQL Server - Added enhancements to more gracefully handle null characters in Plan Guide names by removing the null characters prior to creation in the destination database.

Fixed an issue where the optional Identity Provider ID field for single sign-on (SSO) was required to have a value.

Snowflake - Fixed an issue where subset targets that were specified using percentages resulted in unexpected subset sizes.

SQL Server - Fixed DROP script generation failures that can occur when linked servers exist and SQL_SERVER_SCRIPT_CROSS_DATABASE_REFERENCES=false.