Change Automation Resources
Published 28 August 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 Deployment Suite for Oracle license comes with an entitlement to use automated build and release resources, enabling database DevOps practices like Continuous Integration and Continuous Delivery.
Here is a list of Database DevOps practices along with the required and recommended resources and technologies.
| Database DevOps practices | Description | Enabling resources | ||||||
|---|---|---|---|---|---|---|---|---|
Database build | Get fast feedback and make sure there are not any issues with the scripts in the repository (e.g., invalid PL/SQL syntax, dependency issues, etc.). | Redgate Change Automation build (rca build)
| ||||||
| Static code analysis | Highlights potential issues, provides advice on best practices, and enforces naming conventions. | Redgate Change Automation build (rca build) automatically includes our code analysis checks, learn more about configuring these checks If you are using a Source Control for Oracle, then use Code Analysis for Oracle cmdline (cao.exe) | ||||||
| Database unit testing | Redgate sponsors utPLSQL, an opensource Oracle database unit testing framework. Use this to test your packages, procedures, functions, and more to have more confidence in your releases. | Redgate Change Automation test (rca test) - leverages utPLSQL | ||||||
| Automated release with Redgate Change Control (migrations-based model) | Automatically execute the migration scripts that haven't been run against the target database yet and record their execution in the redgate_schema_hsitory table. In addition, you'll get:
| Redgate Change Automation (rca release prepare and rca release perform) | ||||||
Automated release with Source Control for Oracle (state-based deployment model) | Automatically compare your repository to the target database and apply the schema and static data changes to the target database. | Schema Compare for Oracle cmdline (sco.exe) Data Compare for Oracle cmdline (dco.exe) See a worked example on the Microsoft Dev Blog. | ||||||
| Deployment changes report with Source Control for Oracle (state-based deployment model) | See what objects will be changed in this release and exactly how they will be changed. This is useful for approving a release and provides a history of the changes. (Note: This report is automatically included with Redgate Change Automation.) | Schema Compare for Oracle cmdline (sco.exe) - for deploying schema change Data Compare for Oracle cmdline (dco.exe) - for deploying static data changes | ||||||
| ||||||||
| Deployment warnings report | Get warnings about data loss or potential problems. See the full list of deployment warnings. | |||||||
| Snapshots for rollbacks | Use Schema Compare for Oracle to snapshot your Production database before the deployment. This snapshot can be used in Schema Compare for Oracle as a source to review changes and generate a rollback script to this state. Read more about rollbacks <TODO>. | Schema Compare for Oracle cmdline (sco.exe) | ||||||
| Downgrade scripts for rollbacks | Use Schema Compare for Oracle to generate a rollback script by specifying Production as your source and the repository as your target. Read more about rollbacks <TODO>. | Schema Compare for Oracle cmdline (sco.exe) | ||||||
Note: There are both Windows and Linux compatible versions of the above resources. Learn how to download these from the Deployment Suite for Oracle documentation homepage. Redgate Change Automation is also available on Docker Hub.
For more information and examples about automating database releases see - Redgate Change Automation.
