Toad World® Forums

How to identify the differences between objects in database and VCS

I need to compare objects in the database and objects in my VCS branch, is there any functionality built in Toad Team Coding (Oracle)?

This should include objects controlled and not controlled.

Thank you.

Hi naushad123,

Since Team Coding is designed to provide change control for database objects in a team environment, it doesn’t really make much sense to have it compare DDL for objects that are not controlled. However, there are a few ways you can compare object DDL between the database and VCS for controlled objects.

  1. To compare single objects, simply right-click on the object in the Team Coding Manager window and select “Compare Contents”. You can also click on the Compare button of the object properties window. Team Coding will open both version’s DDL in the compare window.

  2. To compare a specific VCS revision with the database, right-click on the object in the Team Coding manager and select “Properties”. Then click the “Display Revision History” button in the toolbar. 6036.DisplayRevisionHistory.png Select the revision you wish to compare, right-click on it, and select “Compare Contents”. Team Coding will compare that revision’s contents with the DDL in the database.

  3. To compare a list of objects, open the Team Coding configuration window and click on the “Compare and Synchronize” button. 6036.CompareSyncButton.pngYou’ll be presented with the following window:


  • Create new revision in the VCS - Compares the database and VCS source to determine what database changes are not current in the VCS provider.
  • Compile objects in database - Compares the database and VCS source to determine what VCS changes are not current in the database.
    Please feel free to let us know if you have any questions or if there’s anything else we can do.


On a side note, you listed “git” as a tag on your original message. So, you’ll probably want to also make sure your local git repository is up-to-date with your master repository (if you use one) before doing the compare to make sure you’re current with changes made by any other team members.