We have to load 2200+ files per day having 77,000 records per file.
We 3 more jobs running parallely which loads the same amount of records into a different tables.
This job is running in production for the last 2 years taking 11-12 hours to just load into the staging table.
DBA's fear that if I add parallel option to my script it will degrade the other jobs performance n blow the machine.
I tried my best and proved that if I execute parallely (5 parallel streams), the job will complete within in 4 hours.
They asked to to tune my SQL Loader files. I dont have any option.
Just to test.
Only adding the parallel option will do nothing except change the way that free space is used. If there is spare i/o and cpu capacity on the machine then adding more jobs (with parallel set) is a valid approach that they ought not to dismiss without testing
You need to replace the DBA ASAP.
Originally Posted by balajiyes
Click Here to Expand Forum to Full Width