DSXchange

i am asking about updating a type 2 SCD .

Actually the problem is the current date in the table is wrong and i have to update the correct date.

But the table is time variant table. i.e. type 2 SCD if I am not wrong.

Thanx
Sumeet

How Do i update dates in time variant tables. i know that normal update cant be done.
and delete recs whose key is date feild.

Thanks
Sumeet

the shared container is reuseable unit of job which has the set of DS components in it (stages in it). You Create it by first selecting the group of stages you want in it and then going to EDIT tab of toolbar you select for construct conatiner. and your shared container is ready. whenver you use it ...

thanks
I have tried everything with hash file including lock for updates and disbling the cache. I was the one who had posted it. right now performance is not in picture.

Still working on it . any ideas are welcome
Sumeet

thanks for quick answers. yes i am looking up the same hash file. At one place i am creating it and using it for look up to do the insert for any incoming new key columns And at other place i am using it to do the lookup for old keys , so that updates can be done. So it boils down to if any new inse...

I am having a problem with sequencer. when i am running the sequencer it gives a warning Controller problem: Error calling DSRunJob(ScrubClm.), code=-2 [Job is not in the right state (compiled and not running)] now even though the job sequencer is calling has been compiled and has worked properly pr...

Suppose we have this hash file called HASH. This same file is called at two places in the job . This hash is created from target table TGT in which both the insert and update is being done Source table SRC gives out the following columns: Key1, key2, col1, col2,col3 We look up HASH twice . one for u...

I am trying to insert based on primary key lookup. those keys are formed this way: in table2 [b]origin key[/b] 01|A4BZ ----->12345 01|A222 ------>67890 now getting back to the job when i lookup the table2.origin with table1.origin that key and the corresponding row gets inserted. but the problem is ...