Find references to procedures, tables, columns, variables in your PL/SQL Code

Cross-References

Analyze the impact of a change in your code

Estimate what you should modify to accomplish a change.
Don't break your application after a change!

• If I change this variable, what is the effect on my code?
• If I add a parameter to a function, what else is affected?
• If a table or column is changed, which code should I update?
• Etc.

Review CRUD Operations in Your Code

(Create, Read, Update, Delete)

Generate a CRUD matrix, showing which Oracle Objects access your data, and how. For instance, which Procedures Create/Read/Update/Delete which Tables.

• Review dependencies between your Oracle DB and your code.
• Analyze the impact of changing your Schema, for example changing a table definition or adding an index.
• Estimate code complexity and development efforts.
• Find out which tables are never updated, deleted from multiple places, etc.
• Make sure every process has at least one input (R) and one output (CUD).

Explore Complex Chains of Calls

Display callers and callees for procedures, tables, triggers... Navigate through your code.
Understand complex chains of calls. Explore all possible execution paths.
Drill down in the code, click on referenced methods or variables to see their definitions.

Call trees help evaluate the effects of modifications to your code.

Code Comparison

Try a new approach for code comparison:

• Run application-wide comparisons, not only for a file or an object.
• Comparisons are based on the code structure, more powerful than text comparisons
• Browse differences in a container hierarchy. Drill down to find relevant changes.
• Find differences for a given object, or object category: Procedures, Tables, Triggers...
• Find differences within a given container, a Package or a Schema for instance.
• Save “snapshots” of your code on a regular basis, and compare them anytime.