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
Database Compare Suite allows for creating virtual views. These objects store the result of query execution and can be created for all supported relational databases. NoSQL databases do not support them. Virtual views can be included in data operations alongside regular objects.
Database Compare Suite treats a virtual view as a special virtual metadata type. These objects are available only within the scope of the project. All these views are in the virtual views category of the database metadata tree in Database Compare Suite.
This page provides an overview of virtual views and describes the typical workflow of using this type of objects in Database Compare Suite.
To add a new virtual view, right-click on the virtual views category in the database metadata tree. Then select the Create virtual object option from the virtual view menu item.
Then, the Virtual view query editor window opens. Specify the query to define a new virtual view.
Use the following rules to configure a virtual view:
Specify the virtual view name instead of QueryN used by default.
Use the Load script button to upload an existing script from the file.
Press the Load script button to make sure that the script is correct.
Press the Save and close button to create a new virtual view.
Now this virtual view can be used in data operations as a data source. Users can specify all data operation options for a virtual view in the same way as for real objects.
Press the Edit virtual object button to edit an existing virtual view.
Press the Remove virtual object button to remove an existing virtual view from the project.
Database Compare Suite has several limitations for the matching operation. These include:
Matching rules cannot be applied for virtual views.
Columns of a virtual view are always matched to target object columns by ordinals. If the column order in a virtual views does not meet the requirements, you need to edit the relevant query using the Edit virtual object option of the pop-up menu.
Didn’t find the answer?
You can report problems, ask questions or share ideas for improvements on our email [email protected].