RE: PROCESSING APPROACH - Oracle design issue on Unix

[Mercadante, Thomas F]

Title: RE: PROCESSING APPROACH - Oracle design issue on Unix

Paula,

 

Your approach is fine.  The bigger question that your organization needs to ask is - if you leave, can they support it - do they have adequate staff on hand that can maintain PL/SQL code?

 

I agree with you that PL/SQL can do anything that needs to be done for ETL transformation.

 

As I have said over and over again - it always comes down to staffing issues and standards at your site.  If you are a PL/SQL shop, then it's a perfect choice.  If you are a Pascal shop, then it's a really bad choice!  :)

 

Hope this helps.

Tom Mercadante
Oracle Certified Professional

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 29, 2002 1:33 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: PROCESSING APPROACH - Oracle design issue on Unix

Guys,

In the past when writing ETL processes for data warehouses I did a lot with scripting on Unix and used SQL for some basic processing.  I have been moving more into creating stored procedures and also separately been working on modularizing and making generic code.  To me with native dynamic sql, utl_smtp and other Oracle packages/procs available it is cleaner and easier to modularize these codes into different stored procedures.  Thereby I am moving a lot of the code I used to run into stored procs at the same time I am modularizing/generi. it.  Eventually the script will be doing some basic things.  Does anyone have an opinion on the approach I am taking as to its long-term viability/maintainability/reusability?  I would love any and all opinions. 

Thanks,
Paula