DQS Client in SSIS returns invalid status

DQS Client in SSIS returns invalid status by Greg Low - Australia

Active

Type:	Bug
ID:	779183
Opened:	2/13/2013 7:08:32 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Output of the component is not appropriate. "New" seems to override incorrect values.

I have spoken to Gadi Peleg in the DQS team and he agrees that the output is incorrect and that appropriate output would be:

•    If 1 of the values is Invalid – the record is invalid
•    If 1 of the values is corrected – the record is corrected
•    If 1 of the values if New – record is new
•    If all values are Correct – only then record is correct

This is how the DQS client program works but the DQS component in SSIS does not do this.

Details (expand)

English

SQL Server 2012 SP1

Integration Services (DTS)

Not Applicable

US English

In the DQS client, a colleague set up a domain for Australian States and one for Australian suburbs, based on files downloaded from the Aust Post website.
He then created a Data Quality Project to test this. Results are as expected. Hobarrt got transformed to Hobart. Victoria got transformed to VIC. Melburn, New York and NWS all got tagged as New as they couldn't be found. With the Record Status, New seems to gazump Correct, and Corrected seems to gazump them all.

However, in the DQS Client Transform, since Correct gazumps New, unless every field is in error, the record will go to the corrected output. In the conditional split transform, you should just be able to look at the Record_Status to determine what to do with the record, rather than look at each individual field status. While you could look at each individual field status, it would make the conditional split transform unwieldy.

The two tools should provide the same outcome.
You should be able to look at the Record_Status, direct correct and incorrect records to their appropriate destination, then deal with the incorrect ones after the fact. Having the field status in the output would make application error reporting more meaningful as you could nominate the actual field in error.
The main issue is that Correct gazumps New in SSIS, but New gazumps Correct in the DQS Client.

X64

0 attachments

Hi Greg,

Thanks very much for the feedback. We’re closing this issue as “Won’t Fix” because we do not plan to change this behavior in the current release of DQS. We will keep this issue on file for future releases, and will update the Connect item as we have more information to share.

DQS Team