Setting the development source
Published 21 November 2019
Deployment Suite for Oracle has been replaced by Redgate Deploy - Oracle. This page is therefore no longer being updated. For the latest documentation, please click here.
A development source represents a state of the database in your development environment.
There are two types of development sources in Redgate Change Control:
- A development database
- A Source Control for Oracle project
Development database
If your development source is a development database, then you can work directly against this database to safely edit your schema and data using your preferred IDE.
Redgate Change Control will compare your development database against the contents of your project in order to:
- Generate new migration scripts
- Apply migration scripts from other members of your team
Redgate Change Control requires a corresponding shadow database in order to perform these comparisons.
Ensure the shadow database is not an important database! The contents of the database may be dropped and recreated by running the migration scripts in your project while using Redgate Change Control
If you are creating a new project from within Redgate Change Control, the new project wizard will walk you through these settings.
These settings are stored inside the configuration files (.conf) for your project. You can change the development source that your project uses at any time by editing the configuration file.
- The connection string for the database
- The connection string for the shadow database
Set the development source to a database in the .conf
flyway.url=jdbc:oracle:thin:@//localhost:1521/dev1.red-gate.com redgate.shadowUrl=jdbc:oracle:thin:@//localhost:1521/dev1_shadow.red-gate.com
Source Control for Oracle project
A Source Control for Oracle project defines the desired state for a database.
You may wish to use a Source Control for Oracle project as your development source to:
- Have greater control over how the Source Control for Oracle project will be deployed, instead of relying on a state-based comparison at deployment time
- Decouple making changes in development from defining how to deploy them
- Avoid creating a migration script in order to share changes with your team if you're working in a dedicated development database environment
Redgate Change Control will compare the contents of your Source Control for Oracle project against your Redgate Change Control project in order to generate new migration scripts.
Redgate Change Control will need to be configured with a shadow database in order to perform these comparisons.
When setting the shadow database connection ensure it isn't an important database as this will be dropped and recreated by running the migration scripts in your project during the usage of Redgate Change Control
If you are creating a new project from within Redgate Change Control, the new project wizard will walk you through these settings. These settings are stored inside the configuration file (.conf) for your project. You can change the development source that your project uses at any time by editing the redgate.scriptsSource parameter configuration file. The scripts folder is the folder that contains the DatabaseInformation.xml file that was created by Source Control for Oracle and will contain one or more subfolders that contain the DDL scripts for each object.
Set the development source to a scripts folder in the .conf
redgate.scriptsSource=./my_scripts_folder/ redgate.shadowUrl=jdbc:oracle:thin:@//<host>:<port>/<service>
