Automation in the Real World
Oracle Tips by Burleson
With the release of Oracle7 into
the relational database world, Oracle Corporation changed the direction of
system development based on Oracle. Once forced to rely on Oracle*Forms to
include procedural logic that enforced complex business rules, developers
could now enforce these rules inside stored PL/SQL objects.
This was a paradigm shift for Oracle
Corporation and for systems based on Oracle databases. Code stored within the
Oracle7 database enforced system logic, reducing redundant code spread over
multiple applications. This has led to an era of systems development in which
the use of database triggers and other stored PL/SQL objects are planned in
the design phase of systems development.
Despite the importance of this
paradigm shift, the use of stored PL/SQL objects is only one half of database
automation. The other half of database automation, predating even prepackaged
software, involves the use of scripts to accomplish a variety of tasks, such
- • Backup and restoration
- • Creating/maintaining users
- • Dynamic code generation
- • Testing
- • Other miscellaneous purposes
This chapter provides numerous
detailed examples of scripts that accomplish a variety of purposes, as well
as numerous examples of stored PL/SQL objects. Familiarity with the actual
tasks performed in the examples is useful, but not absolutely necessary.
This is an excerpt from the book "High
Performance Oracle Database Automation" by
Jonathan Ingram and Donald K. Burleson, Series Editor.