Redgate Change Control needs to communicate with the following databases:

• Development database
• Shadow database (learn more)
• Target database to use for baseline (optional)

The format for the connection information used to connect to these databases is the same in each case. The information may either be specified when prompted in the UI or can be set directly in the project settings file or user settings file.

Schemas

The list of schemas to track within the database must be specified for all database types.

It is currently expected that these schemas will be the same across all databases used within Redgate Change Control. The one exception to this is that if only a single schema is being tracked when using Oracle, the shadow database can be set to a shadow schema instead, removing the need for an extra database.

A flyway_schema_history table will be added to the first schema in your list to track migration scripts that have been run on it.

Connecting to Oracle Databases

The following parameters are needed when connecting to Oracle databases:

• JDBC URL: the standard JDBC URL format for Oracle databases.  Examples:
   jdbc:oracle:thin:@//<host>:<port>/<service>
  jdbc:oracle:thin:@<tns_entry>
  See Oracle official documentation.
• Username: the username to use to connect.
• Password: the password to use to connect.

Connecting to SQL Server databases

The following parameters are required when connecting to SQL Server Databases:

• JDBC URL: the standard JDBC URL format for SQL Server databases. Example:
  jdbc:sqlserver://<host>:<port>;databaseName=<database>
  See SQL Server official documentation.

Note that Redgate Change Control currently supports the following authentication types:

• Integrated (Windows authentication)
• SQL Password
• Azure Active Directory Integrated
• Azure Active Directory Password
• Azure Active Directory Interactive (see Using Azure Interactive Authentication for details)

For SQL Password and Azure Active Directory Password, a username and password also need to be provided.

For Azure Active Directory Interactive, a tenantId and clientId need to be provided.