SQL Server flat file import/SSIS flatfilesource import file LocaleID is not installed error problem

When using SQL Server and SSIS to import a CSV file to a database recently (SSIS chooses FlatFileSource as the source of the data stream), you always encounter the LocaleID 4 is isn't installed on this system. this error.

Later, long time found that there was a problem with the locale option selection on FlatFileSource, because the CSV file to be imported contains Chinese, so the sqlserver/ When SSIS imported CSV, I chose Chinese (Simplified) on the FlatFileSource locale to prevent Chinese entry into the database as garbled (as shown), but the client's database server was installed in English Windows Server 2008, there is no Chinese language pack in the operating system, so when you select Locale as Chinese (Simplified) in FlatFileSource in sqlserver/ssis, SQL Server is in Windows The language pack for Chinese (Simplified) was not found in the server system, so there was an error in the above.

To solve this problem, you must first understand the SSIS server on which the operating system installed the language pack, and then the most important point is that as long as the code page in the FlatFileSource is set to the correct encoding to solve the Chinese import database after the problem of garbled, You can select a good code page in the FlatFileSource preview first, if the preview of the data is not garbled so the data should not be garbled. In this example, I found that the client server operating system does not support the locale of Chinese (Simplified), but supports the locale of Chinese (People's Republic of China), Change the locale of FlatFileSource to Chinese (People's Republic of China), and then make sure that the code page is set to 936 and I successfully import the CSV file into the database without garbled characters.

SQL Server flat file import/SSIS flatfilesource import file LocaleID is not installed error problem