Red Gate logo

Fewer errors. Greater transparency.

Lightning fast deployment.

Source Control for Oracle

Source Control for Oracle

Regular price: $369

+
Schema Compare for Oracle

Schema Compare for Oracle

Regular price: $495

+
Data Compare for Oracle

Data Compare for Oracle

Regular price: $495

=
Deployment Suite for Oracle

Deployment Suite for Oracle

$869

Introduction to Deployment Suite for Oracle

Get all our Oracle tools at a 30% discount

  • Take the complexity out of recording schema changes in Subversion or Team Foundation Server.
  • Compare and synchronize schemas. Deploy changes from source control. Automate for continuous integration using the SQL Automation Pack.
  • Compare table data fast and generate update scripts without writing a single line of SQL.
Download 28-day free trial

Pricing information

$869

per user

Buy now

Key features of the Deployment Suite for Oracle

Compare schemas and data fast

Quickly and clearly see differences in schema objects and table data across instances of your database.

  • Compare multiple schemas and tables at once.
  • See differences in the DDL for schema objects.
  • A graphical view of rows and columns highlights where data is out of sync.
  • Filter comparison results and generate interactive reports.
Compare schemas and data fast
Deploy database changes accurately

Deploy database changes accurately

Generate update scripts without writing a single line of SQL.

  • Synchronize environments using the software or save deployment scripts to review and execute in your IDE.
  • Group objects or select individual changes.
  • Get deployment notifications about dependencies, truncations, and other issues.
  • Deploy changes from any version in source control.

Source control database code easily

Take the complexity out of recording schema changes in Subversion or Team Foundation Server.

  • Checking in changes is as simple as writing a log message and clicking a button.
  • Use the difference viewer to inspect every change before you check it in.
  • Get notifications about new changes.
  • See who modified the database and why, and access a history of every change.
  • Compare your database to past revisions in source control.
Source control database code easily
Automate tasks with the CLI

Automate tasks with the command line interface

Access the functionality of Schema Compare and Data Compare through the command line.

  • Automate scheduled tasks like comparisons and deployments.
  • Include in your build system for continuous integration (you'll also need the SQL Automation Pack).

What our customers are saying

Case study

Case study

How Techwan SA saves time with the Deployment Suite for Oracle

We speak to Louis-Philippe Normandin, DBA and DB Architect at Techwan SA, about how easy it was to install and use the Deployment Suite for Oracle, and the benfits for Techwan SA and their customers.

Read the case study (PDF)

Continuous integration

Continuous integration (CI) is the process of ensuring that all code and related resources in a development project are integrated regularly and tested by an automated build system.

Code changes are checked into source control, triggering an automated build with unit tests and early feedback in the form of errors returned. A stable current build is consistently available, and if a build fails, it can be fixed rapidly and re-tested.

If you want to get started with continuous integration for your database, you'll need the SQL Automation Pack.

Introduction to database continuous integration

A CI server uses a build script to execute a series of commands that build an application. Generally, these commands clean directories, run a compiler on source code, and execute unit tests. However, for applications that rely on a database back-end, build scripts can be extended to perform additional tasks such as creating and updating a database.

The diagram illustrates a typical integration process. The automated continuous integration process begins each time the server detects a change committed to source control by the development team.

Continuous integration ensures that if at any stage a process fails, the ‘build' is deemed broken and developers are alerted immediately.

ci-oracle-continuous-integration-process

Database code

Database code is code, and should therefore be treated in the same way as your application code. However, the principal difficulty underlying continuous integration for databases is the lack of a simple way to keep a database in source control and deploy it to a target server.

The database is unlike application code in as much as it contains a state that needs to be preserved after an upgrade. Where a production database already exists, DML and DDL queries modify the state of a database. Unlike application code, there is no source code to compile. Deployment therefore relies on creating upgrade scripts.

The lack of database source code makes it difficult to maintain a current, stable version in source control. Creation scripts can be checked into the source control repository, but despite their importance, the disciplined creation and on-going maintenance of these scripts is not often considered a core part of the database lifecycle.

Where changes are deployed to an existing database, all differences and dependencies must be accounted for. In some production deployments, this involves multiple targets with different schemas and data. The manual process is time consuming, prone to errors, and one that should not be left unresolved at the end of the project cycle.

Benefits of database CI

Keeps your database up to date

Databases may figure in your CI process because the application code requires a database to function correctly. The database schema version corresponds to an analogous application code version. Any changes to the application code or the database structure could, in theory, break the system. Consequently, they should trigger the CI process.

Once a database is maintained in source control, Red Gate tools can build a clean database from its source files to accompany the application build.

If you already have internal test databases that need to match the development databases, you can keep them up to date with the latest version, using continuous integration.

Verifying database deployment scripts

Developers get immediate feedback on each change they commit to the database scripts. If the build fails, they know exactly which change caused it to fail.

Free educational content

We're committed to providing Oracle education to all

From our webinars with Oracle experts, to the independent community at All Things Oracle, we aim to give you the best resources on a whole host of Oracle topics.

Free webinars presented by leading Oracle experts

Regular new webinars and an expanding archive where you can re-watch past webinars - all for free!


A SQL Performance Problem Seek and Destroy — Mostly Destroy

Karen Morton

December 5th, 2014 - 10:00-11:00 AM CST

Register now

It’s usually not difficult to find SQL that is performing poorly. The hard part is what to do with a bad SQL statement once you have it. In this session, Karen Morton will show you how to use a simple method that is reliable and repeatable for solving any problem SQL statement you might encounter.

This is an interactive session. Ms. Morton will begin by reviewing a problem SQL statement that she has chosen to illustrate the method she’ll demonstrate. But the star of this show will be you. We invite you to join brimming with questions that will extend the content of the lecture and demo.

Oracle Database In-Memory in Action

September 17th, 2014

Download video

Join three of the brightest minds in the industry: Cary Millsap, Kerry Osborne, and Tanel Poder, for a one-hour webinar as they discuss the revolutionary technology of Oracle Database In-Memory, an in-memory column store that does not slow down the OLTP components and is compatible with all existing applications.

Oracle APEX Webinar: I Want Master / Detail / Detail, and I Want It Now!

May 15th, 2014

Download video

Application design patterns offer developers reusable solutions to common problems. In enterprise applications, the Master / Detail pattern provides end users with an intuitive and efficient means to work with data models that have header records with one or more detail records. Oracle APEX has included native support for the Master / Detail pattern for a while, but for some people it’s not enough - they need Master / Detail / Detail.

View more webinars

Community of experts

Check out All Things Oracle for content from the leading names in the Oracle community.

Visit All Things Oracle