Search found 7 matches
- Wed Nov 06, 2013 9:21 pm
- Forum: IBM QualityStage
- Topic: Reference Match Performance
- Replies: 2
- Views: 4441
- Wed Nov 06, 2013 8:06 am
- Forum: IBM QualityStage
- Topic: Reference Match Performance
- Replies: 2
- Views: 4441
Reference Match Performance
We have a reference match on standardized address and area data. The reference data set has 25 million rows, and loads into the job at only 1700 rows per second. There are only 12,000 rows at a time in the source data set. Can the experts please share ways to improve the performance of a reference m...
- Thu Oct 31, 2013 4:27 pm
- Forum: IBM QualityStage
- Topic: Problems with Reference Match
- Replies: 1
- Views: 3729
Problems with Reference Match
I am having several problems with QualityStage match designer, and wonder whether I'm doing anything wrong. Whenever I leave the match designer by clicking OK the changes are saved OK, but DataStage Designer immediately stops working. I have to close it and open a new one (after waiting for a period...
- Thu Oct 17, 2013 10:09 pm
- Forum: IBM QualityStage
- Topic: Match Designer Database
- Replies: 1
- Views: 3737
Match Designer Database
Can Teradata 13 be used for the QualityStage Match Designer database? It tests successfully when configuring the Test Environment in Match Designer, but throws syntax errors when attempting to test a match pass. ##E IIS-DSEE-TDOD-00007 15:03:54(002) <main_program> [IBM(DataDirect OEM)][ODBC Teradata...
- Thu Oct 17, 2013 1:49 am
- Forum: IBM QualityStage
- Topic: Cleansing Data before Standardization
- Replies: 7
- Views: 8085
I am using QualityStage but, because there is so much extraneous information and so many different ad hoc formats, the AUAREA and AUADDR rule sets are proving quite poor at parsing out significant information. There are some 377 different input patterns using AUAREA rule set. Over 30% of records hav...
- Wed Oct 16, 2013 6:32 pm
- Forum: IBM QualityStage
- Topic: Cleansing Data before Standardization
- Replies: 7
- Views: 8085
I have a DataStage job that splits the string at the first street type token in the data; the token and all preceding it go into the addr bucket while everything following the token goes into the area bucket. If no street type token exists then all the data go into the area bucket. Using character i...
- Wed Oct 16, 2013 2:19 pm
- Forum: IBM QualityStage
- Topic: Cleansing Data before Standardization
- Replies: 7
- Views: 8085
Cleansing Data before Standardization
Hi, I've got some really dirty Australian address data, with lots of "added" information. The entire address is in a single VarChar field with no consistent format. Can you suggest ideas for cleansing the data (using DataStage, with which I am quite familiar) or QualityStage? I am permitte...