Next: Another Embarassment For The U.S. Patent Office. Previously: Roggio’s Daily Reports.

Mystery Date Crisis Solved

98 words.

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.

Related

Next: Another Embarassment For The U.S. Patent Office. Previously: Roggio’s Daily Reports.

This page is a static archival copy of what was originally a WordPress post. It was converted from HTML to Markdown format before being built by Hugo. There may be formatting problems that I haven't addressed yet. There may be problems with missing or mangled images that I haven't fixed yet. There may have been comments on the original post, which I have archived, but I haven't quite worked out how to show them on the new site.

Sorry, new comments are disabled on older posts. This helps reduce spam. Active commenting almost always occurs within a day or two of new posts.