The step output column sequence in the SSIS execution variable is different from the SQL query column sequence.

This problem was encountered by a friend who made an SSIS program to import data to txt. Then, use Oracle tools to import data to Oracle. However, when performing the variable step in SSIS, we can find the output column name and the queried column name.

This problem was encountered by a friend who made an SSIS program to import data to txt. Then, use Oracle tools to import data to Oracle. However, when performing the variable step in SSIS, we can find the output column name and the queried column name.

This problem was also mentioned in a Blog later: The SSIS series-variable query statement causes inconsistent column output sequence.

You can use the following method:

The solution requires manual operations, but it is much easier to delete new columns in the File Manager. To return to the data source column, cancel all available columns first.

Then, select the required columns in sequence based on the query statement column sequence. For example, check BusinessEntityID first and NationalIDNumber second, and then select the columns in sequence as needed.

After the selection is complete, all columns are output in the query order.

You need to re-create a new file link manager to avoid the impact of the previous cache. Then you can see that the column order in the Manager is consistent and there is no problem.

This article is from the "follow SQL Server Technology" blog. Be sure to keep this source