DSXchange

Thanks for the input Naveen! Any thoughts on how this design will perform when there is large amounts of data? Won't the first potentially produce a huge amount of data that has to be processed by the Transformer? Say table A has 3 mill rows, and that each of these hits 100 rows in table B, that wil...

Hi! I am trying to implement a join between two tables with history in Datastage. In sql I would do something like: select * from tableA a left outer tableB b on a.key = b.key and (a.valid_from_date between b.valid_from_date and b.valid_to_date or b.valid_from_date between a.valid_from_date and b.va...

Hi! Anyone have some tips or best practice on how to implement SCD type 6 dimension loading in Datastage? My case: I have a large profile table that is incrementally loaded with combination of codes and their corresponding descriptions each day. If a code gets a new description this should be reflec...

If I have two or more links going into a DB2-connector, will whatever the first link does be rolled back if the second link fails? E.g. if I first do a delete operation, and then an insert, and the insert fails, will the delete be automatically rolled back? If not, is there any quick way of fixing t...

I have checked the lengths, they all match, so that is not the source of the problem.

I get the following warning when using the PXPivot-stage in a job: "When checking operator: When binding output interface field "TYPE" to field "TYPE": Implicit conversion from source type "string" to result type "string[max=1]": Possible truncation of va...

I guess my scenario is pretty common: I have a source database which has a log table that indicates that table x, y, z (and so on) is ready to be loaded into my DWH. The tables get ready at different times during the night, and I would like to be able to 1) load them one-by-one as they get ready, or...

I'm running a parallel job with an ODBC connector to update a table in an SQL Server database. The update statement is read from file. The job always runs fine, and reports back "Number of rows consumed by the user-defined SQL statement: x". But, sometimes it takes longer than usual to run...