DSXchange

I think, Pivot stage can be used as long as you have same number of records for each key column group.

All, I need to build a calendar with in datastage to generate surrogate keys for time dimension. I know datastage has in-built calendar but need to build a calendar from Given start date to end date using datastage functions. Is anyone accomplished this before? If so, Could you let me know the optio...

Database is remote. I can't understand the resposne perforce. Is that performance?

How can the state file perform well..could you explain in detail?

Is there any performance bottle neck for one vs other?

I mean datawarehouse project Ray. Also, like surrogate key genration best practices and complex flat file best pratices would help for this.

What are the best practices for datastage dataware porject? Please provide ,May be some very high level with some level of details.

can we use datastage complex file stage for all mainframe source files? or can we use sequential file to read mainframe source files? Under what situations we have to use sequential file stage vs complex flat file stage for reading mainframe source files? Is there any performance implication on one ...

As far as best practices front,

Is State file better option than DB sequence for surrogate key generation?

If so, Why?

Did you use two outputs of SCD or just one? If not, what are the observations on the two inputs? what that really contains and how we can use?

Can we get updates separately and inserts separately using parallel SCD stage?

I think, SCD gives all changes and new records in the update dim output link with either existing or new surrogate key.
What is the other output really contains? Is this other output mandatory even if I don't need that for processing?

dd

ddd

That means, I have to use copy stage to expose that one reference file into mutiple files and then able to pull the required fields to the output. Right? Also, How does it work with AND condition and OR condition? Like, we have in server, If I have mutiple reference links on one lookupstage, I have ...

As we know lookup stage can handle multiple reference files in one stage. I need to confirm the following, - Same table with different source columns and with the same reference columns matching, Can I use one lookup stage to populate different output fileds using the one key field from the reference?

SCD Stage wouldn't support if source physically deletes the record on their side. SCD works with Source file as the driver for the lookup process inside SCD to figure out the dimension changes. The best way to identify those records are..anything which is on history and not on the source file would ...