Oracle provides a binary wrapper utility that can be used to scramble PL/SQL source code.This utility was introduced in Oracle7.2 (PL/SQL V2.2) and is located in the ORACLE_HOME/bin directory.This will allow you to easily revert to previous code should someone make any catastrophic changes.

In more recent releases both triggers and procedures are compiled when created (stored p-code) and one can add as much code as one likes in either procedures or triggers.

However, it is still considered a best practice to put as much of your program logic as possible into packages, rather than triggers.

SQL is a declarative language that allows database programmers to write a SQL declaration and hand it to the database for execution.

As such, SQL cannot be used to execute procedural code with conditional, iterative and sequential statements. PL/SQL is Oracle's Procedural Language extension to SQL.

Not to mention the numerous PL/SQL enhancements made in Oracle 10g and 11g.

PL/SQL and Java appeal to different people in different job roles.Some of the differences: Both PL/SQL and Java can be used to create Oracle stored procedures and triggers.This often leads to questions like "Which of the two is the best?PL/SQL's language syntax, structure and data types are similar to that of Ada.Some of the statements provided by PL/SQL: Conditional Control Statements: The PL/SQL language includes object oriented programming techniques such as encapsulation, function overloading, information hiding (all but inheritance)." and "Will Oracle ever desupport PL/SQL in favour of Java? Many Oracle applications are based on PL/SQL and it would be difficult of Oracle to ever desupport PL/SQL.