Source Control for Oracle is a Windows application that makes it easy to version-control your schemas with SVN and TFS. You can continue making changes in your IDE without the need to work on separate script files, so there's no disruption to the way you work.
Source Control for Oracle checks your changes into version control for you — so you don't have to rely on manual scripting and source-controlling processes. You can compare changes to source control and see highlighted differences. When you're ready, just type a message and click Check in.
The History tab shows every change, so you can easily track which objects were changed, who checked them in, and when. Each object can be compared before and after check-in with the differences viewer. If something went wrong with your latest change, the difference viewer makes it easy to spot and fix.
Source Control for Oracle works independently of your editor, so whether you use SQL Developer or PL/SQL Developer, you don't have to change how you work on your database. Minimized, the tool keeps the team up-to-date through task bar notifications while you work.
If your team works on a shared development database, you can lock objects while you work on them. If someone tries to edit an object, the server will return an error message. Comments can be added when locking objects to aid communication across the team.
Source Control for Oracle makes setting up sandboxed environments easy. Developers can get the latest version from source control before starting work to make sure they're not overwriting other people's changes. When a new person joins the team, it's simple to get them up and running with a fresh copy of the database in source control.
Source control (also known as version control or revision control) is the management of changes to a file or set of files.
Source control systems do many useful things:
Normally, workarounds are needed to make sure developers have the latest database changes. That means discussing updates in person or email, and pausing development until everyone's up to date. Some development teams share work with backups and restores, or a custom in-house solution. These are usually time-consuming and subject to human error.
With source control, your team can quickly get the latest changes and commit their own. It's easy to track who changed what, when they did it, and why. If conflicts occur, you can compare the differences before committing a change.
Without source control, it's easy for a database change to accidentally lead to an overwritten table, data loss, or a bug, even in projects with single developers modifying a simple database. Again, the problem is amplified in teams.
Source control systems reduce the likelihood of disasters by increasing the transparency of the development process and helping you catch bugs early. If problems do occur, mistakes can be easily undone by reverting to a previous version.
Normally, resuming partially completed work can be slow. Developers have to spend time understanding each other's code and the state of the work. For large or distributed development teams, this problem is amplified.
By allowing developers to easily document their changes in a source control system, teams can easily review the history of a project, getting up and running much more quickly.
Many organizations are required to comply with regulatory standards, including the Sarbanes–Oxley Act and the Statement on Auditing Standards No. 70: Service Organizations (SAS70). Databases contain critical data, so compliance auditors usually require organizations to account for every change to a database.
By source-controlling databases, it's easy to:
Redgate's dedicated source control tool for Oracle databases, Source Control for Oracle, connects your database directly to your SVN or TFS source control system. By automatically storing a complete history of your Oracle database schema changes, Source Control for Oracle makes implementing source control easy.
Another Redgate tool, Schema Compare for Oracle, lets you compare and deploy changes from the files under source control, useful for spotting changes, reverting to a previous version, and deploying upgrades.