1.0 Introduction

2.0 Problem Definition

 (Note: DOB column (Datatype: DT_DBTIMESTAMP) has two date formats (DD/MM/YYYY & MM/DD/YYYY).)



        And when the above file extract the above file, data in the table looks like below.

    Observations:

• I expected the 06/26/1988 value extraction to fail because of the poor data quality (It should have been 26/06/1988)

• I wanted 03/04/2013 value to be interpreted as 3rd April 2013, but it is inserted as 4th March 2013.

3.0 How does it work

        
        SSIS expects every date value to be in MM/DD/YYYY format & if it has an issue converting, then it assumes it to be in DD/MM/YYYY format. Hence 20/06/1988 didn’t fail & 03/04/2013 inserted as 4th March 2013.

        If it couldn’t convert a date value to either of the formats (DD/MM/YYYY & MM/DD/YYYY), for example, 13/13/2008, then it throws an error “Data conversion failed: The value could not be converted because of a potential loss of data."

(Note: The above behavior is the same even if you use a Data conversion Transformation.)

4.0 Solution

                
        We can overcome this default behavior of SSIS by declaring the Flat file source Datetime column datatype as String & Using DateTime.ParseExact () Function of C# to convert the string value to a specific Date format. (If the conversion fails, the error rows can be redirected to Error File. (Like Below)

Override the Input0_ProcessInputRow Function in the script component

 Note: The Date format in the above code (Highlighted in Blue) can be sourced from Package configurations (SSIS String Variable). More about the format strings can be found here.