Software Applications Programming Errors and solutions.

Issue: I want to check out this error that didn't show me while using the SQL Server 2008 version and its sql server business intelligence studio to create packages. Currently in the company we have migrated to SQL Server 2017, but when trying to execute a package with the SQL Agent (jobs) I get this mistake. Thing that never happened before. Suggestions: 1.This problem is of incompatibility with packages version before. 2.having a different bit version of windows and sql server or SSIS (64/32) can present issues. Reinstall/upgrade to 64 if possible.

Issue : This error come  before when migrate data from oracle to SQL server using SSIS ? Error Column "Col1" cannot convert between unicode and non-unicode string data types Solution: The column is coming back as unicode and then either being loaded into a non-unicode (varchar) column in the table, or possibly set to output as non-unicode in the oracle source (or non-unicode to unicode). Try putting a data conversion component in the data flow between the source and destination, and set data_1 column to match the type and width of the target table/column.