bdbafh_at_gmail.com wrote:
> this post does not directly answer your question, but I think that its
> worth considering.
>
> In addition to whatever source control your developers use ... a
> bastard dba from hell would log all changes to all source for each of
> the app_owner schemas via database triggers. This would not log
> developer's changes to code in their own schemas - only those applied
> to the app_owner schemas in development.
>
> You could do the same thing in your qa and prod dbs, but you don't
> allow developers to make changes to the packages there directly ... do
> you? They're not supposed to ... until that urgent issue or emergency
> comes along and policies get tossed.
>
> Log the source changes and you'll have both an audit trail (nice for
> SarbOx) and the source to restore without having to go to dump files,
> etc.
>
> setup a specific account for this, give it its own tablespace, prevent
> DML upon the logging table by other users.
>
> -bdbafh
The real BDFH builds a DDL trigger that raises an exception with all DDL
on the database and another that audits it. He/she then disables the
first trigger whenever making changes leaving the second one to create
the audit trail.
--
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)
Received on Sat Mar 05 2005 - 17:28:44 CST
