Posted: Fri Jan 14, 2011 2:01 pm Post subject: db2 table partitions
Normally, loading those many records will take more time. Contact your DBA and get how the target table defined, i.e, normally based on table key , they will split the table into partitions. If that is true , get the partition info from DBA. load each partition separately to process the jobs faster.
1. Total size of data, based on Record size ( total no of records * total size ) - 1 million records and 1300 Record length
2. No of applications going to use this data concurrently - Probably less than 4 jobs will access this database concurrently.
Normally, in batch process , for reporting purposes.
many shops use VSAM files to store data. They schedule all jobs in such a way , once VSAM file got created, those jobs will run one after another to generate reports.
If your scenario is similar to what is explained above.. you can go for VSAM.
if your data will be used by production applications, better go for db2 for
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum