Limit the number of records

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vij
Participant
Posts: 131
Joined: Fri Nov 17, 2006 12:43 am

Limit the number of records

Post by vij »

Hi,

As i wanted to limit the number of records to be loaded in a job, i used this option - job properties -> exectuion -> force complie

here, i faced a problem, all the limited records which are read by the datastage, are being wriiten to the log and so it takes more time and occupies more server space too...

can anyone pls let me know is there any way i can avoid this or suggest other solution to limit the records to be loaded in the job.

Thanks,
ajith
Participant
Posts: 86
Joined: Thu Nov 10, 2005 11:10 pm

Re: Limit the number of records

Post by ajith »

Not clear what is your exact requirement
Is it to load less number of rows to the target?
in that case head or tail stage would do.
I am not getting what you did in force compile as it never gives any options to limit the rows

sorry that I am not getting your requirement, please clarify
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Force compile to reduce records :roll:
Are you getting confused with DumpSore?
What is your job desing?
While running the job, you will have the limits like 'Stop stages after n rows' you can use that.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

There are lots of ways to do this. What does your job design look like? The best way is not to extract rows in the first place. Another possibility is a Head or Tail or Sample stage. What precisely are your requirements?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
trobinson
Participant
Posts: 208
Joined: Thu Apr 11, 2002 6:02 am
Location: Saint Louis
Contact:

Post by trobinson »

I would ask why the limited records are being written to the log. Could it be there is a Constraint on the link of Otherwise? Perhaps a Peek stage is capturing the rejected records in the Director logs? If it isn't needed, remove it and let the rejected records fall on the floor. Better yet write them to a Sequential file.
Post Reply