How to run a Server job by setting a row limit

pongal · Post by **pongal** » Sun Mar 14, 2004 9:59 pm

Hi guys.... :D
i wanted to know how to run a job by setting row limit.
i am running a job where source(database table) having 70 lac records.
i wanted to check first 100 rows how the records were transformed to target.
is there any constraint or predefined command to limit the rows while passing to target.

kcbland · Post by **kcbland** » Sun Mar 14, 2004 11:03 pm

If you are running the job from Director or the Designer debugger, the invocation dialog box has a tab that allows you to set the limit of rows.

If you are using custom job control, there is an API to call after you have attached a job handle. Look in your DS BASIC manual, I think it's called DSSetJobLimit.

ray.wurlod · Post by **ray.wurlod** » Mon Mar 15, 2004 12:24 am

There are a few possibilities.

Ken mentioned setting a row limit in Director when submitting the run request. This can also be accomplished, in various ways, with the other ways of submitting a job run request, for example the dsjob command line interface.

The down side to this approach is that the job's exit status will be Stopped, which means you'll need to reset it.

While you're still in the development environment, why not constrain the Transfomer output link with (@INROWNUM <= 100) in addition to any other constraints? Of course this does mean that your job will read the entire 70 lakh records (for the non-Indian folks, that's 7 million), but you will then get some feel for how long that will take.

Yet another possibility is to use the Debugger to step through the job design a row, or even a link, at a time. You can, by varying the breakpoint expression, determine when the job is to pause. And the watch window will, provided they are in context, allow you to see column values going into and coming out of a Transformer stage, so that you can determine that transformations (and link navigation) is or is not proceeding according to how you believe it should. You can stop the job run in Debugger (instead of processing all 70 lakh input rows) and re-compile as a quick way to reset.

chulett · Post by **chulett** » Mon Mar 15, 2004 8:30 am

Another possibliity!

Create a 'local' copy of the table (perhaps in your own schema / workspace) and populate it with only 100 of the rows from your source table. Fast and easy to work with it when it's bite sized.