DSXchange

If you are writing to a sequential output file you can funnel both your output links back together again. They should have the same column metadata.

If you are talking about retrieving these keys to satisfy foreign key relationships of subsequent dependent loads then you just do a fresh database lookup to retrieve the new keys. If you want to get just the new IDs back then do as Ray suggests and filter on the process id or date fields that shoul...

This usually happens when you set the "Output mode" to "Single row" on the Transformation Settings tab of the output stage. To quote the help file "Single row. Select to generate one XML document per input row."

If you switch to "Aggregate all rows" you get one XML document for all input rows.

Is your field trimmed? I would expect a char(10) to come through as "FLIGHT " or " FLIGHT" instead of "FLIGHT".

If your development team has been disciplined and always loaded in your Teradata column definitions from the same saved table definition then you can find a list of jobs by running Usage Analysis on that table definition from the DataStage Manager Tools menu. However this is often not the case, or t...

I don't know about an Extended Edition of DataStage but the Enterprise Edition comes with parallel jobs and MetaStage.

Taking an SCD type 2 table as an example there are three additional requirements over a normal table that take up resources. They store much more information, which impacts on (cheap) disk space, index size and performance. Every update to this table is two transactions, an insert of the new current...

A lookup is not that much of an overhead for a parallel job since it caches it in memory. Since the value does not change for each row it would be more efficient to pass it in as a job parameter or invocation id. The easiest way to retrieve a value from a database via a sequence job is the good old ...

You used to be able to get a download link to a version 6.0 multiple job compiler when you joined www.tools4datastage.com. I don't think you can get to that any more but there is a version floating around out there somewhere.

How many DWs can tell you the quality of the quantity?

Are you using materialised views? What do you like about them? Our project is considering using DB2 materialised views for reports instead of queries against tables. One particular features looks very useful, the ability to freeze the view to a snapshot even when the underlying tables are being upda...

Just noticed that even though you posted in the server forum you already have an enterprise license. Because your DataStage and Oracle are using the same server you may need to scale your DataStage nodes down during the day so you don't pull resources away from online users and then ramp it up at ni...

1) You can do everything on the one DataStage server (and it will certainly save you a lot in licensing fees!). If you are concerned about scalability and whether your poor little server can handle the volume of four marts then consider upgrading to enterprise edition, increasing the CPUs and RAM or...

Have a look at the FAQ on DataStage reporting to see what options you have:
http://www.dsxchange.com/viewtopic.php?t=93565

We use DB2 sequences and not DB2 identity columns. I am not sure which is better. If I had a choice I would go for ETL generated keys every time. We have issues with DB2 sequences, we have to fudge the insert SQL to make it retrieve NEXTVAL from the sequence to generate an id, it can be difficult to...