FAQ:SSIS:Known Issues: Difference between revisions
Jump to navigation
Jump to search
Created page with "__FORCETOC__ ==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 Ma..." |
No edit summary |
||
| Line 1: | Line 1: | ||
__FORCETOC__ | __FORCETOC__ | ||
==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. | :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. | ||
Revision as of 19:14, 5 March 2014
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.