Breaking Changes to Integration Services Features in SQL Server 2005
New: 17 July 2006
This topic describes changes made to SQL Server 2005 Integration Services (SSIS) after the initial release of SQL Server 2005 that could cause applications based on earlier versions of Integration Services to break.
Previously Successful Column Conversions May Fail
After you apply SQL Server 2005 Integration Services (SSIS) Service Pack 1 (SP1), column conversions may fail in the following cases:
| Column Conversion | Issue Description |
|---|---|
Conversions from String to Unsigned Integer |
If you have negative numbers in string columns (DT_STR or DT_WSTR) and convert the column data type to an unsigned integer data type (DT_UI1, DT_UI2, DT_UI4 or DT_UI8) the package previously ran successfully, and the negative values were converted to 0. After you apply SP1, the package no longer converts negative values to 0, but instead returns an error and the package may fail. Applies to: Lookup transformation, Fuzzy Lookup transformation, Fuzzy Grouping transformation, and the Flat File source. |
Conversions from String to Binary |
If you have characters in string columns (DT_STR or DT_WSTR) that are not convertible to a byte array, and you convert the column data type to the DT_BYTES data type, data might be silently corrupted; that is, the value of the column is converted to an array of zeroes. The installation of SP1 adds the UseBinaryFormat property to the Flat File source to help interpret binary data. After you apply SP1, when UseBinaryFormat is set to false (the default value), if a column contains characters that cannot be converted, the conversion generates an error, and packages that previously ran successfully now may fail. Applies to: Flat File source. |