MicrosoftHi all,
we have just migrated our development data warehouse server from SQL Server 2017 to SQL Server 2019 including about 300 SSIS-Packages using the Attunity Connector. I'd like to share our experience and raise some questions. First of all the Microsoft Connector is now generally available and the official blog article is here: General availability of Microsoft Connector for Oracle. I will also post a copy of this comment over there.
LDAP support
Most important thing first: there's no LDAP support. Tim.Chen Zoe_Luo Chunhua frugecn steveo1770 : are there any news on this?
Performance
Performance seems to be identical to the Attunity Connector. Very few packages were running about 10-20 percent slower, but they were not running under the usual enviromental conditions. We will keep an eye on this.
[Microsoft][ODBC Oracle Wire Protocol driver]Invalid character value. Error in column 3.
Most of the migrated packages were running out of the box. About 10% of the packages generated an error like shown above in the source component (only the column number varied). The only solution to solve this behavior was recreating the source component in the data flow. I have briefly compared the SISS package's XML before and after and found no apparent differences. Any ideas on this?
I have found a related blog post: https://docs.microsoft.com/en-us/answers/questions/359442/error-adding-new-column-ssis-2019-ms-oracle-source.html
[Microsoft][ODBC Oracle Wire Protocol driver]Unable to convert column 2. Cannot convert from SQL type 93 to C type 2.
One single package returned in this error in the source component on execution. The solution to the problem was the same than above: recreate the source omponent in the dataflow. Any ideas?
[OLE DB Destination [14]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "The statement has been terminated.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Invalid data for type "numeric".".
On being executed one single package resulted in this error in the destination (!) component. The corresponding Attuntity version doesn't show this error. I have identified the column responsible for this error and its metadata is the same in both versions of the packages. Any ideas on this?
Thank you for reading and I'm looking forward to your comments,
Gerald
