Requirement to filter first run to generate following days

laknar · Post by **laknar** » Thu Jan 29, 2009 7:45 am

i have a attribute called code.

if the code is 1 then filter for the first run.
from the next run if the code is 1 then we have to flow to the target.

kandyshandy · Post by **kandyshandy** » Thu Jan 29, 2009 8:36 am

Can you be more clear with your requirements?

What do you mean by first run? first run for the day or first run (Initial load) on production environment? Similarly, you may want to explain about next run too!!

laknar · Post by **laknar** » Thu Jan 29, 2009 10:25 pm

Hi,

First run is the Initial load the records should not flow into the target.
for the next load records has to flow into target.

vasa_dxx · Post by **vasa_dxx** » Thu Jan 29, 2009 10:56 pm

Reject the records on code=1, write to a file/table. Use this file/table for lookup for the second run.
Further Runs depend on your requirement.
So what is the case for for third,fourth,.... runs.

laknar · Post by **laknar** » Fri Jan 30, 2009 12:12 am

next load we need to flow into target.
if we reject in the first load and the next day also will get reject.

ray.wurlod · Post by **ray.wurlod** » Fri Jan 30, 2009 1:07 am

Stop.

Step back.

Analyze thoroughly what you want to occur, with examples, on day one and on subsequent days. Document the rule under which the cycle resets to day one.

From this analysis produce a detailed specification.

Get someone else to review your work (peer review).

This process ought to make it much more clear how to go about the ETL design.