SSIS differing behaviour between XP and Server 2003 -
04-11-2006
, 12:41 AM
We have a complex SSIS package that works perfectly on Windows XP SP2 with
SQL Server 2005 Developer Edition, but when we import the package into SQL
Server 2005 Standard Edition running on Windows Server 2003 the package fails
execution, with errors regarding truncation of data imported from an Excel
Spreadsheet.
We had similar errors on XP until we discovered how to configure the
appropriate size for target objects. Once we configured everything with the
correct sizes the package completes without error on the XP machine.
When we import the package into SSIS on the test server running Windows
Server 2003, one step in the package fails reporting that imported data would
be truncated.
We have opened the package file in the editor on the test server, and run it
in debug mode, and indeed when it reaches the step in question it fails.
When we check the step details the size of one column appears to be reset to
the default of 255 and no matter how many times we change it to the correct
size, save and execute the package, it fails and we find it has reverted back
to 255 when viewing properties. |