Hello,
    I have a SSIS package that loads data from a text file into a table in SQL Server. The table is first truncated, then the data is loaded. This has worked fine for the last 18 months. On Friday, while our application server was under stress (IIS was eating up most of the RAM), SSIS decided to put blanks in the table during the load. Funny thing was it loaded the same number of records as in the text file, only the fields were all blank (unlike the file which had perfectly good data in it). We ran the same package again later (after spending considerable time finding the missing data), and the same files loaded fine. Very strange. Only thing is that during the time of the bad loads, the server was under stress.

    The SSIS package is simple. It truncates the table, then loads the data. There are no special transformations or variables going on. Only a text file source and an OLEDB destination in the transformation task. I would of hoped that if SSIS was having troubles, that it would not load anything. I have logging enabled and it didn't even show any errors. Package does error out correctly when text file is bad in normal circumstances.

Any ideas??

We are using SSIS on a Windows 2003 64bit machine with SQL 2005 SP3 64 bit version. The destination SQL Server 2005 box is 32 bit.

I would hope that in this case SSIS would error out and not load anything. It loaded blanks which caused us a huge production incident. I have written a proc that runs afterwards to check for blank data, however I don't believe I should have to do this.

Thanks in advance,


Jeremy