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

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 779183 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/13/2013 7:08:32 PM
Access Restriction Public


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.
Sign in to post a comment.
Posted by Microsoft on 2/21/2014 at 11:39 AM
Thanks for bringing this to our attention. This has been fixed. The change will be included in a future release or servicing release for SQL Server.
Posted by Microsoft on 4/15/2013 at 5:55 PM
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