Hi Everyone,
I have a simple that extracts data from DB2 database and loads in to sql server.Iam using DRS stage for both the source and target databases. The job is taking 12 minutes of time to process 2 million of records. I would like to bring down the processing time under 8 minutes . I wonde why but we dont have DB2 EE stage so we have to use either DRS stage or ODBC EE stage .. Even i tried to read the data through the ODBC EE stage but no luck. Could anyone suggest how to read the data parallel from db2 database by using DRS or ODBC EE stage . And my db2 database is not partitioned.
Thanks in Advance
How to read data parallel from DRS and ODBC stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 13
- Joined: Fri Mar 14, 2008 4:30 pm
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Very doubtful. All stage types are supplied with DataStage. Did "someone" elect not to install them all?pradkumar wrote:But we dont have DB2 native stage to use.
Why not use DB2 Enterprise stage? It can automatically pick up the table's partitioning information and effect parallel SELECT on that basis. Parallel SELECT is not available for non-partitioned tables.
ODBC (including DRS selecting ODBC protocol) does not inherently support parallelism. If you are selecting from a partitioned table, then it may establish multiple connections to the database to read from each partition. But otherwise there are no parallel-read options using ODBC.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
No, no-one has suggested that. What they have suggested is that the DB2 Enterprise stage inherently supports parallelism, whether that will improve anything or not is a whole 'nuther kettle of fish.pradkumar wrote:So from your suggestion only thing to improve the performance is to use native DB2 stage to read the data.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi,
Ray -- My apology for the wrong information i gave .. We do have DB2 stages in the palette but DB2 EE stage is not configured. Perhaps our DB2 tables are not partitioned. My admin is working on configuring the DB2 EE stage . So if i use the DB2 EE stage how will that effect the parallel read (since db2 tables are not partitioned). The job is simply extract and load, i dont understand exactly why its taking 20 mins to load 2 million records ( iam doing truncate and insert) . how to find the bottleneck in the job and any suggestions to improve ..
Thanks
Ray -- My apology for the wrong information i gave .. We do have DB2 stages in the palette but DB2 EE stage is not configured. Perhaps our DB2 tables are not partitioned. My admin is working on configuring the DB2 EE stage . So if i use the DB2 EE stage how will that effect the parallel read (since db2 tables are not partitioned). The job is simply extract and load, i dont understand exactly why its taking 20 mins to load 2 million records ( iam doing truncate and insert) . how to find the bottleneck in the job and any suggestions to improve ..
Thanks