Re: Sqlldr versus inserts
- From: Mladen Gogala <mgogala@xxxxxxxxxxx>
- To: JDunn@xxxxxxxxx
- Date: Mon, 12 Mar 2007 08:48:36 -0400
On 03/12/2007 07:52:43 AM, John Dunn wrote:
> We currently load large amounts of data into a table using sqlldr which
> is run from a unix script initiated from a java stored procedure.
> The application designers want to eliminate the script and load the data
> directly using java and jdbc, which I presume will mean using insert
> statements.
>
> Sound like a bad idea to me from a performance point of view, but am I
> correct? If not using sqllldr what oprions are there to read a flat file
> and inseet the data. Will external files give the same performance as
> sqlldr?
>
First, you should have added Perl to the mix. If you have Java and shell script
in
the mix, there is no reason not to have a Perl script in there, too.
Second, JDBC can handle array inserts and direct inserts. There is absolutely
no reason to call either a shell script or a SQL*Loader. Third, yeah, loader
will
be faster then sqlplus, for most of the cases. Now, how about having Java code
call
shell script which calls Perl interpreter? Sounds optimal to me.
--
Mladen Gogala
http://www.mladen-gogala.com
--
http://www.freelists.org/webpage/oracle-l
- References:
- Sqlldr versus inserts
- From: John Dunn
Other related posts:
- » Sqlldr versus inserts
- » Re: Sqlldr versus inserts
- » Re: Sqlldr versus inserts
- » Re: Sqlldr versus inserts
- » RE: Sqlldr versus inserts
- » RE: Sqlldr versus inserts
- » RE: Sqlldr versus inserts
- Sqlldr versus inserts
- From: John Dunn