Regarding Dynamic blocking in Quality Stage

Infosphere's Quality Product

Moderators: chulett, rschirm

Post Reply
suguna
Participant
Posts: 15
Joined: Wed Jan 31, 2007 6:57 am

Regarding Dynamic blocking in Quality Stage

Post by suguna »

Whenever doing blocking we have to specify field block how can we do dynamic blocking....Is there any other ways we can give blocking fields by DataStage .....Thanks in advance.... :)
Regards,
suguna
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard. :D

There's no such thing as dynamic blocking in QualityStage.

You select one or more blocking fields in each match pass. For records even to be considered for matching, the blocking field values must be the same. Running multiple match passes with different blocking fields can help to reveal matches that were not discovered with other blocking fields selected.

For example, blocking on street name will miss matching records where one has a street address and the other has a PO box address, even though the records are for the same person. Blocking on NYSIIS of last name will (probably) match that particular pair of records.

For "blocking", understand "grouping".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Alexander
Participant
Posts: 17
Joined: Fri May 12, 2006 10:10 am
Location: Europe

Post by Alexander »

I don't understand what's you are trying to solve.

In QS, the blocking fields are fixed, they don't change dinamic. What you define in the developer, is what you get in the execution.

The only way is to create a Match stage with n steps and n Blocking fields, that will be fill in DS using different constraints.

Or use a field with code and another field with value, and use this two fields in blocking stage. the pairs with same code and value will match.

But keep in mind, empty blocking fields doesn't match.
Post Reply