Data Quality Services:Notice: Difference between revisions
Jump to navigation
Jump to search
Created page with "← Data Quality Services Customers leveraging the DQS client within SSIS to consume our services may run into an issue where additional columns ..." |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Data Quality Services|← Data Quality Services]] | [[Data Quality Services|← Data Quality Services]] | ||
==Additional Returned Columns== | |||
Customers leveraging the DQS client within SSIS to consume our services may run into an issue where additional columns that are over and above the address will return in a single, large group of text data. This presents problems if one is interested in these additional fields of information, as many data columns may contain commas as well – such as Census columns, or results codes. This can break the parsing of this data. One of 3 resolutions is recommended in these cases: | Customers leveraging the DQS client within SSIS to consume our services may run into an issue where additional columns that are over and above the address will return in a single, large group of text data. This presents problems if one is interested in these additional fields of information, as many data columns may contain commas as well – such as Census columns, or results codes. This can break the parsing of this data. One of 3 resolutions is recommended in these cases: | ||
Latest revision as of 20:21, 10 August 2016
Additional Returned Columns
Customers leveraging the DQS client within SSIS to consume our services may run into an issue where additional columns that are over and above the address will return in a single, large group of text data. This presents problems if one is interested in these additional fields of information, as many data columns may contain commas as well – such as Census columns, or results codes. This can break the parsing of this data. One of 3 resolutions is recommended in these cases:
- Use Melissa Data SSIS components which are programmed specifically to integrate with our Web services in the SSIS environment. This is often faster, and can give functionality above that of the DQS client.
- Use a script component within SSIS to connect to our web services or local libraries to cleanse data.
- Use the script component to connect to the azure service and pull back the specific columns of data.