The fastest method should be with SQL Loader using Parallel, Direct Load
with no logging. Since this precludes the use of triggers, I have typically
loaded first into temp tables, verify that that load went OK and that the
data is good, (if not I could do a quick re-load!)then used inserted into
the production tables. I'm unsure what's causing the problem with your
connections, possibly some sort of time-out? I have run Oracle on NT and
Unix with hundreds of connections, without unexpected disconnects.
Steve Brown
J. R. Baker <jrbaker_at_ccgate.hac.com> wrote in message
news:370D34A9.8AE60546_at_ccgate.hac.com...
>My group is trying to jam data into ORACLE as fast as possible.
>We get the data from a flat file, generate INSERT statements,
>and send them to ORACLE 8 using OCI calls (in MS C++).
>
>This works, but we are looking for speed. One way we
>increase speed is to launch multiple threads on the
>client and open a database connection per thread. This
>works great in SYBASE and perhaps less great in ORACLE.
>
>One problem is: we have lots of triggers in our database.
>If we turn triggers off, the data loads 5 times faster.
>This implies a server-side bottleneck. Right ?? Any
>ideas ??
>
>Another problem: When we get above about 15 connections,
>ORACLE just loses a connection now and then. Even when
>the connection has already been running a while, Oracle
>just seems to lose it. Anyone seen this type of thing
>before ? It seems much less graceful than Sybase. Sybase
>was able to go to 50 connections with no problem and
>was very well mannered if you asked for too many.
>
>Thanks in advance for any advice on these topics.
>
>John Baker
Received on Fri Apr 09 1999 - 00:04:09 CDT
