F.A.Q.: Technical Questions

The setup package is zipped archive. Before installing, you need extract ALL the archive content into any folder on your computer. The installation error you describe appears usually when user trys to run CDBInstall.exe executable directly from zipped archive.

In most cases the issue is caused by termination of the current connection by database server. For some reason database server can terminate the current connection without sending any notification to the client.
Contact your DBA and check the database server configuration.

• In most cases the issue is caused by incorrect configuration of the current connection.
  Check whether the provided connection info - database server host name, username and password - is valid.
• Another reason of the issue can be usage of incompatible ODBC driver.
  Check whether the driver you are using allows working with your database.

1. Be sure that the user whose credentials you are using for connecting to the data source has enough permission to see the schema tables. Contact your DBA if needed.
2. Try to change your database connection settings:
   1. Open the Connection properties dialog box: right-click on the connection and select Properties command
   2. At the General tab:
      1. explicitly specify the type of the database that you are connecting to:
         find the Database Type dropdown list at the bottom of the dialog select the appropriate type
   3. At the Settings tab:
      1. find the Schema Mode dropdown list and select All user's authorized schemas
      2. find the Quick loading metadata support dropdown list at the bottom of the dialog and select Disable
   4. At the Advanced tab:
      1. check Support SQL_ALL_SCHEMA option
      2. check Support SQL_ALL_TABLE_TYPES option

this is a test

The possible reasons for the situation are:

• The user, whose credentials you are using for connecting to the data source, has no enough permission to see the system schema tables.
  Please check permissions of the user. Provide the user with more permissions, if needed. Contact your DBA if needed.
• Some database engines - MS SQL Server or Oracle, for example - show only those stored procedures, that are defined under the schemas having the name equal to a user name registered in the database, even if the current user has full administration permissions.
  On the database side, create the users having the name equal to the schemas you are going to work with.
• The predefined SQL queries used for getting list of stored procedures and their bodies are not matching version of the database engine you are connecting to.
  1. Use Tools › SQL Vendor specifics menu command. The SQL Vendor specifics is dispalyed.
  2. Select the type of the database you are working with from the Database Source Type dropdown list
  3. Redefine the SQL statements in Query string "Stored procedures list" and Query string "Stored procedures list"

1. Make sure that the tables you compare have same columns number. Disable the odd column if the tables column number is different.
2. Make sure that the tables columns are mapped correctly