DSXchange

Thank you Craig and Ray. I was trying to avoid doing this one job at a time, but it seems I have no choice. Believe it or not, we just upgraded to 8.1, so I don't think 8.7 is in our near future. :)

I have been looking for a way to generate a report of all jobs that have been executed in a project in the last 90 days. I know all the jobs are not running and I want to clean up the environment by removing the jobs that have not been executed in a while. Please help or point me to a discussion tha...

Thanks to everyone for their generous input. I have decided to to stagger the job run times. I am marking this topic as resolved. Thank you once again!

Jay.

Thanks to everyone for their generous input. I have decided to to stagger the job run times. I am marking this topic as resolved. Thank you once again!

Jay.

If the jobs are staggered, this situation will not arise because the logic looks up existing keys before assigning new keys. So if the streams are staggered, one stream will insert new surrogate keys. The next stream will find existing keys and new keys if not found in the first stream. This works a...

Hi Ray. Thanks for your response and information regarding how the Hashed File Stage works. I agree with you regarding the fact that the logic is dangerous. That is why I was looking for an alternative that would be cleaner. We can't use two separate Hashed Files because the Hashed File is used as a...

I am trying to clean up some existing jobs. There are 2 feeds coming in from different systems. Each of them has CUSTID as the primary key. There is a hash file (CUST_ID.hsh) that contains the CUSTID along with a generated Surrogate Key (DWH_CUST_ID). The jobs are using SDKSequences to maintain the ...