RE: SQL*Loader vs External Tables
- From: "Mercadante, Thomas F" <thomas.mercadante@xxxxxxxxxxxxxxxxx>
- To: "'charlottejanehammond@xxxxxxxxx'" <charlottejanehammond@xxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 3 Nov 2004 14:12:15 -0500
Charlotte,
The biggest benefit that I see is the reduction of one step in a data load
process.
Normally, we would load data (using sqlldr) into a staging table, and then
use PL/SQL to process that staging table.
With an External table, I can eliminate the first step, and use PL/SQL
directly against the external table.
Others might have better observations than this.
Good Luck!
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
From: Charlotte Hammond [mailto:charlottejanehammond@xxxxxxxxx]
Sent: Wednesday, November 03, 2004 12:09 PM
To: ORACLE-L
Subject: SQL*Loader vs External Tables
Hi All,
I am about to set up a regular data load process. In the past I've done
this using SQL*Loader but I'm thinking of inserting from an external table
instead. I believe the underlying stuff is much the same but wonder if
there were any pros and cons of using external tables over SQL*Loader for
regular scheduled loads. It's a pretty straightforward load (not lots of
ETL type stuff) of data directly into columns so being able to do it with
PL/SQL is a small, but not huge benefit.
Thanks for any comments.
- Charlotte
---------------------------------
Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com/a
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
