Database Compare Suite™
- Product features
- Getting started
- Connecting to server
- Connecting to an Amazon DynamoDB database
- Connecting to an Amazon Redshift database
- Connecting to an Apache Cassandra database
- Connecting to an Azure SQL Database
- Connecting to an Azure Synapse Analytics data warehouse
- Connecting to a BigQuery data warehouse
- Connecting to a Greenplum database
- Connecting to an IBM DB2 database
- Connecting to an IBM Netezza database
- Connecting to a MariaDB database
- Connecting to a Microsoft Access database
- Connecting to a Microsoft SQL Server database
- Connecting to a MySQL database
- Connecting to an Oracle database
- Connecting to a PostgreSQL database
- Connecting to a Snowflake database
- Connecting to a Sybase ASE database
- Connecting to a Sybase IQ database
- Connecting to a Teradata database
- Connecting to a Vertica database
- Installing the required database drivers
- Creating a new project
- Opening an existing project
- Key activation
- User interface elements
- Connecting to server
- Operations in details
- Schema comparison
- Schema synchronization
- Schema operations options
- Data comparison
- Detailed data comparison
- Fast data comparison
- Data synchronization
- Data migration
- Settings comparison
- Virtual views
- Sorting key selection
- Selecting operation scope
- Matching rules
- Fast data comparison options
- Data operations options
- Command-line interface
- Known issues
The first step of all data operations is the matching rules wizard. By default, Database Compare Suite creates the pair for metadata objects with the same type, name, and parameters (for stored procedures and functions). Using the matching rules, the user can change this default behavior and specify the custom rules to build desired pairs.
By default, the dialog box does not include any custom rules. Click the Add button to open a rule creation dialog. There are 4 rule types that the user can specify.
Manual matching rule
The manual matching rule allows users to match any pair of compatible metadata objects regardless of their location under the operation scope.
Please note that the paths in the manual matching rule should start from the root object. This is the database or the schema for platforms that don’t support database level.
Category matching rule
The category matching rule allows users to match the same family categories in the source and target databases.
Find the family categories in the table below.
|Family type||Included objects or categories|
|Data objects||Table, View, MaterializedView, Partition, ExternalTable, FlexTable, FlexExternalTable|
|Routine objects||Procedure, Function|
|Schema level objects||Schema, Package|
Consider using this option to match different categories of objects on one side and a single category of objects on another side. For example, when you have tables and views on a source side and only tables on a target side. Without the matching rule, you should manually match each view from the source database with a relevant table from the target database. After you set up the category matching rule, Database Compare Suite can automatically match views and table regardless of the number of objects in these categories.
Object selection rule
Object selection rule allows users to include or exclude selected objects from the operation. The objects can be selected by metadata type, using a list of names or a filter mask.
You can set the following options for this rule:
Side — defines the side to apply the filter. You can set the following values for this option: Source, Target, Both. If you exclude metadata objects only on one side, they will be included in operation on the other side. Use the both value if you want to exclude or include objects both from the source and target databases.
Action — objects can be included in operation or excluded from the operation. If you specify at least one include rule, then all not included objects will be excluded from the operation.
Mode — defines the rule to filter metadata objects. The exact name option means that metadata objects’ names will be filtered by their exact names using the list of names in the filter field. In the SQL pattern mode, the comparison of the metadata object names is based on a SQL pattern similar to the LIKE operator.
Filter — uses the list of names in the Exact name mode or a pattern in the SQL pattern mode. The names can be imported from a text file.
Import Filter — the user can load a list of filtered object names from an external text file. The names in this file should be separated by comma or placed in different rows.
Name conversion rule
Name conversion rule allows users to match the source and target objects with different names using the transformation of source object name by a specific pattern and replacement and comparing with the target object name.
Source and target metadata types may not be the same but should relate to the same family (see the description of families in the category matching rule).
Didn’t find the answer?
You can report problems, ask questions or share ideas for improvements on our email [email protected].