We are pleased to announce the general availability of SQL Comparison Toolset 9.0 for Oracle. Existing users may upgrade to this version through the Idera Customer Portal. New users may download the trial version from the Idera Website.
Accelerate your DevOps workflows with IDERA SQL Comparison Toolset. Easily automate and propagate database schemas from development through staging to production. Around the world, DBAs and developers managing the movement of database versions through their organizations save hundreds of hours and achieve much higher levels of precision and accuracy through IDERA SQL Comparison Toolset.
Now supporting Oracle 18c and 19c!
Both schema and data support the new Oracle 18c and 19c.
Data Compare Command Line Wizard
The new command-line wizard simplifies the creation of the command line XML config file.
Schema Compare Command Line
The previous release of the toolset didn’t include a command line for the schema compare.
Schema Compare Command Line Wizard
Intended to simplify the creation of the command line config file.
A new and unified interface for all Oracle connections used by schema, data and the command lines. These connections include a few changes:
It adds the option to have Oracle-specific connection settings.
It can check the validity of these settings.
It no longer supports the TNS connection type, mainly for simplicity.
Data command line includes an option to encrypt Oracle credentials and the data source stored in the command line config file. This same option is also supported by the schema command line.
Data command line supports the UTF32 file encoding. The previous supported UTF7 encoding has been removed.
Data compare script no longer drops triggers or foreign keys that are disabled. Disabled constraints have no impact on the synchronization process.
Data command line no longer requires the schema in the object name.
Schema filters have been simplified. They are intended to provide object exclusion. Initially, it was detailed that they would perform both inclusion and exclusion, which made them confusing.
Schema compare no longer collects information about tablespaces, data files, and temp data files. The Oracle views that contain this information require admin permissions and failed in most cases.
Schema compare now collects the current user and the user schema from the user context. The Oracle views used in the previous version needed admin permissions.
Data compare now sets the transaction isolation level to READ COMMITTED. This works much better than the previous setting, which was Serializable. READ COMMITTED is also the Oracle default value.
A fix in the trigger script now shows the trigger status in schema compare. This is useful when the triggers are disabled.
Change in the definition parsing of views, procedures, functions, packages, types, and triggers fix some rare issues related to scripting of these objects.
Schema compare now supports the schema triggers (similar to the DDL trigger on SQL Server)
The help file has been updated. This includes updates for the new command line feature.