Sequential file Vs Database

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
coolkhan08
Participant
Posts: 25
Joined: Wed Oct 13, 2004 1:11 am

Sequential file Vs Database

Post by coolkhan08 »

Hi,
We have to ftp a file from mainframe. It has around 400 thousand rows. I wanted to know if I should use a database temp table or use a sequential file as temp storage of this file, before further processing. On using target as sequential file it was around 39MB. What is good performance wise.
Thanks.
Sam
chucksmith
Premium Member
Premium Member
Posts: 385
Joined: Wed Jun 16, 2004 12:43 pm
Location: Virginia, USA
Contact:

Post by chucksmith »

If all you are doing in the next processing step is reading the file, then always use a sequential file. Otherwise, the choice is between a hash file or a table.
trokosz
Premium Member
Premium Member
Posts: 188
Joined: Thu Sep 16, 2004 6:38 pm
Contact:

Post by trokosz »

One angle is if your processing this data sequencially then nothing beats the performance of a sequential file vs. database. Another angle is if the intent is to persist the data vs. deleting this at the end of the Job then the database is the best option.
coolkhan08
Participant
Posts: 25
Joined: Wed Oct 13, 2004 1:11 am

Post by coolkhan08 »

Thanks for the replies. I think a sequential file would be good for temp storage and then use a hash file too to run look ups on it later on. I am creating both a sequential file and a hash file same time from the transformer stage when ftping from the source mainframe.
Post Reply