Endgame Viable

To follow up on yesterday’s mystery date problem: It turned out that one of the incoming dates had been erroneously entered with the year “1007” instead of “2007.” The date was valid on the Oracle data source, and it was valid within the SSIS data flow. However, SQL Server 2000 can’t store a date prior to the year 1753, so the data destination failed. I put in a script component to test for dates earlier than 1753, set them to “1/1/1753”, and flagged the row with an error. Now all is working without the icky “ignore errors” setting.