Search found 53125 matches
- Mon Jul 28, 2008 4:22 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Help on cartesian product in DataStage server job
- Replies: 17
- Views: 12581
- Mon Jul 28, 2008 4:19 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SAP metadata not correct
- Replies: 1
- Views: 817
- Mon Jul 28, 2008 4:18 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Disabling Local Message Handlers
- Replies: 13
- Views: 4204
- Mon Jul 28, 2008 4:16 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Command execute activity
- Replies: 12
- Views: 4056
- Mon Jul 28, 2008 4:13 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Message
- Replies: 1
- Views: 716
- Mon Jul 28, 2008 4:11 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Fatal Error : Invalid start timestamp entered
- Replies: 1
- Views: 922
- Mon Jul 28, 2008 4:08 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Partitioning in Filter stage
- Replies: 1
- Views: 868
With only six rows nothing you do will make a lot of difference. What partitioning (Auto) uses depends on what's upstream of the Filter stage. Hash partitioning may worsen performance if it causes your data to be skewed (you have, for example, many more NY than NJ). The Filter stage does not use the...
- Mon Jul 28, 2008 4:04 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Teradata Installation
- Replies: 13
- Views: 3117
- Mon Jul 28, 2008 4:00 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: oracle update option
- Replies: 2
- Views: 964
It does whatever you ask it to do. But "it" here is not DataStage - DataStage simply sends the data to the database in an "UPDATE" context. If the primary key is the same, the row is the same. This is stock standard SQL behaviour - nothing at all to do with DataStage and how it works. If the primary...
- Mon Jul 28, 2008 3:55 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: NVARCHAR TO VARCHAR
- Replies: 2
- Views: 1275
- Mon Jul 28, 2008 3:53 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Read sequential variable length file
- Replies: 5
- Views: 2514
- Mon Jul 28, 2008 3:49 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: reading file with special characters in its name
- Replies: 4
- Views: 1254
- Mon Jul 28, 2008 3:47 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How to get the Rank and AVG
- Replies: 1
- Views: 702
DataStage is not a reporting tool. You would ordinarily use regular SQL to get these answers. An Aggregator stage can give you an average (mean). Rank is more difficult, particularly when you have not specified how you wish tied ranks to be handled. An ETL approach would typically involve sorted dat...
- Mon Jul 28, 2008 3:44 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Configuration file
- Replies: 1
- Views: 582
The number of logical nodes is the number of nodes named and defined in the configuration file. You should have more than one configuration file; one that can use all of the server machine's resources and some other, smaller ones, that can be used when not all of those resources are required (for sm...
- Mon Jul 28, 2008 3:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sparse look up usage
- Replies: 1
- Views: 713
No, you can use sparse lookup at any time, whether or not you have checked the memory. It is the least efficient option, and is intended for use only when the reference data set is known in advance to be too large to fit in virtual memory. Note that sparse lookup can not be selected dynamically, so ...