Difference between revisions of "FAQ:SSIS:Known Issues"

From Melissa Data Wiki
Jump to navigation Jump to search
Line 1: Line 1:
__FORCETOC__
[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
==SSIS: Matchup - Date Keys are Not Being Built Correctly==
==SSIS: Matchup - Date Keys are Not Being Built Correctly==
:When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format, causing the Date Key to not be built.
When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format, causing the Date Key to not be built.




:;Future Resolution
;Future Resolution
:We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.
We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.




[[Category:Known Issues]]
[[Category:Known Issues]]
[[Category:SSIS:Data Quality Components]]
[[Category:SSIS:Data Quality Components]]

Revision as of 21:15, 7 October 2014

← SSIS:Data Quality Components


SSIS: Matchup - Date Keys are Not Being Built Correctly

When using the Component Type: Date in your MatchCode, Date Keys sometimes do not get built in the MatchKey. This is due to a conflict in the expected input format for Dates. Date Inputs should be in the format 'yyyMMdd'. This becomes problematic particularly for some DBMS. SQL Server for example may have a Date Column defined with char[30]. This causes trailing spaces to be included in the Date Input which conflicts with the expected Input Format, causing the Date Key to not be built.


Future Resolution

We will be adding a fix in a later build to trim the trailing white spaces for Date Inputs.