Database Compare Suite™
- Overview
- 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
- Matching rules
- Fast data comparison options
- Data operations options
- Command-line interface
- Settings
- Requirements
- Known issues
- Support
Command and connection timeout parameters
You can change command and connection timeout parameters for the Database Compare Tool application. They are listed in the configuration file DBBest.DataSuite.Application.exe.config, which is located in the root of the application folder. To make changes to command and connection parameters, you have to edit this file.
Open the configuration file DBBest.DataSuite.Application.exe.config from the root of the application folder.
Command timeouts are listed in the following rows:
<add key="access.command.timeout" value="0"/> <add key="azure.command.timeout" value="0"/> <add key="azuredwh.command.timeout" value="0"/> <add key="cassandra.command.timeout" value="0"/> <add key="db2.command.timeout" value="0"/> <add key="dynamo.command.timeout" value="0"/> <add key="bigquery.command.timeout" value="0"/> <add key="greenplum.command.timeout" value="0"/> <add key="mariadb.command.timeout" value="0"/> <add key="mysql.command.timeout" value="0"/> <add key="netezza.command.timeout" value="0"/> <add key="oracle.command.timeout" value="2147483"/> <add key="postgresql.command.timeout" value="0"/> <add key="redshift.command.timeout" value="0"/> <add key="snowflake.command.timeout" value="0"/> <add key="sqlserver.command.timeout" value="0"/> <add key="sybasease.command.timeout" value="0"/> <add key="sybaseiq.command.timeout" value="0"/> <add key="teradata.command.timeout" value="0"/> <add key="vertica.command.timeout" value="0"/>
You can change values of command timeouts for each database platform.
Connection timeouts are listed in the following rows:
<add key="azure.connection.timeout" value="30"/> <add key="azuredwh.connection.timeout" value="30"/> <add key="cassandra.connection.timeout" value="30"/> <add key="db2.connection.timeout" value="30"/> <add key="dynamo.connection.timeout" value="30"/> <add key="bigquery.connection.timeout" value="30"/> <add key="greenplum.connection.timeout" value="30"/> <add key="mariadb.connection.timeout" value="30"/> <add key="mysql.connection.timeout" value="30"/> <add key="netezza.connection.timeout" value="30"/> <add key="oracle.connection.timeout" value="30"/> <add key="postgresql.connection.timeout" value="30"/> <add key="redshift.connection.timeout" value="30"/> <add key="snowflake.connection.timeout" value="30"/> <add key="sqlserver.connection.timeout" value="30"/> <add key="sybasease.connection.timeout" value="30"/> <add key="sybaseiq.connection.timeout" value="30"/> <add key="teradata.connection.timeout" value="30"/> <add key="vertica.connection.timeout" value="30"/>
You can change values of connection timeouts for each database platform.
Please note that the timeouts are specified in seconds. 0 value means infinite timeout. For Oracle command timeout, you can use values from 1 to 2147483; zero value for command timeout can be used in ODAC 12c Release 1 and later versions.
Didn’t find the answer?
You can report problems, ask questions or share ideas for improvements on our email [email protected].