) Code Page in SSIS

Code Page in SSIS

MSDN interprets Code Page as follows: For character and Unicode data, the Code Page defines the bit mode that represents a specific letter, number, or symbol (for example, 0x20 represents a space, 0x74 represents the character "t "). Some data types Use one byte for each character. The bit mode of each byte can be one of the 256 different bit modes.

 

During Data Coversion of SSIS projects, we often encounter problems like this:

The column "xxx" cannot be processed because more than one code page (1252 and 936) are specified...

This problem is usually prompted on the Destination control (such as ole db Destination), both the Data import Destination and the Data Flow Task control, this means that during conversion matching, the character set defines more than one code page. However, when the Destination control problem is solved, the problems on the Data Flow Task control will be solved, because the Destination control exists in the Data Flow Task control.

The solution to this problem is to set the alwaysusedefacodecodepage attribute of the Source control (such as ole db Source) to true.

However, I found in my experiment that setting the Properties window on the right side of Visual Studio IDE does not work. Right-click the OLE DB Source control and Click Show Advanced Editor...

 

 

After this setting, the problem is solved.

In the pop-up window, select Component Properties and set the attribute alwaysusedefacodecodepage to true. The value of DefaultCodePage should also be 936.