We have the an issue with our .dtsx packages developed in BIDS 2008 and deployed on SQL Server 2008 R2.that import data from .csv flat file connections. We do not have the issue in our DEV environment hinting that the problem may be environmental. The DEV server version is Microsoft SQL Server 2008 R2 (RTM) - 10.50.1790.0 (X64) Apr 22 2011 11:55:34 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor) PROD does not have the Cumulative 4 Pack on yet and it is on that server where the last record of the .csv is skipped.. We will be putting on the cu soon, but it is not a known issue fixed in this KB. PROD version: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor) The only other environmental difference is the 64-bit version of the Office Tool Kit was installed on the PROD server, but not DEV The import files are .csv and there are no apparent anomalies in the column delimiters or designated row identifier (even for the last row). When running one package as part of a job from the SQL Agent, the last record is skipped every time. Text qualifier is set to none. We are baffled. Anyone with a resolution or work around?

I guess you tried to process the same file in DEV and it works. Can we see the end of the file how it looks like? I think you overlooked something and it is not a product related issue. I am also sure you get a warning message but do not capture it because you have no logging implemented in that package, right, yes? If so, I suggest the following approach: Go add extra good logging to the package and if you get a warning post it here Arthur My Blog

Arthur, You are correct, we attempted to import the same file in DEV and there was no issue. We will add logging to the package in production and let you know the warning that we capture. The last record of files have CR LF characters like all the other rows and the cursor is on the next blank row when viewed in a text editor.