Thanks much Ernie for the advice.
Somehow building up sqls to dig ourselves is much flexible than using tools i guess. I am a novice when it comes to various informationServer peripheral tools .... i hope i figure out what Metadata Workbench has to offer.
Search found 6 matches
- Thu Aug 16, 2012 5:59 am
- Forum: General
- Topic: Retrieving data from DS8.1 xmeta tables
- Replies: 12
- Views: 42770
- Wed Aug 15, 2012 7:27 am
- Forum: General
- Topic: Retrieving data from DS8.1 xmeta tables
- Replies: 12
- Views: 42770
Columns and Data types
XMETA is disappointingly hard to decipher. Wondering if anyone figured out a way to join the XMETA table "DATASTAGEX_XMETAGEN_DSCOLUMNDEFINITIONC2E76D84" (provides column names and properties ) to a table that provides JOB NAME and/or STAGE NAME. I am on lookout for list of jobs that has c...
- Thu Feb 23, 2012 3:00 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD stage - new dimid for updates
- Replies: 7
- Views: 3436
I have specified two columns as business keys. The lookup succeeds because I can see that my type 1 columns are updated. The problem is that my surrogate key also gets updated with a new key. I could exclude the dim id/surrogate key for update in the update part of the upsert. But then the dimid in ...
- Wed Feb 22, 2012 5:33 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD stage - new dimid for updates
- Replies: 7
- Views: 3436
- Tue Feb 21, 2012 9:24 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD stage - new dimid for updates
- Replies: 7
- Views: 3436
- Tue Feb 21, 2012 2:28 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD stage - new dimid for updates
- Replies: 7
- Views: 3436
SCD stage - new dimid for updates
While trying to laborate with the scd stage, I ran into the following. The scd-stage sends update and inserts to the upsert link. My problem is that every record gets a new dimension id. This is ok for new records, but not for updates. I thought that updates would keep the old dimid. The problem her...