MicrosoftHave upgraded SSIS package from SQL2017 to SQL2019 and the majority of Oracle data sources transitioned from Attunity to Microsoft's connector without issue. A few (4 out of 33) failed at runtime. Needed to remove and re-add columns from the Oracle data source to get them to run. From examination of the package XML I couldn't see any difference (other than the order with the package XML), so that was strange.
We now have a lot of the data sources raising warnings at runtime that the external columns are out of synchronisation with the data source. This seems to happen to every column that maps to a DT_WSTR data type, and can't seem to correct it be rebuilding the data tasks. Also when the package starts we have the initial validations (33 tasks + package validation log entry) before the "Beginning of package execution" log entry. This has increased from approx. 20 seconds to 60+ seconds. Not a problem as this an single overnight execution of the package, but a noticeable increase from Attunity. To early to tell how the overall performance has changed with the switch from SQL2017 to SQL2019.
