MicrosoftWe are experiencing performance issues with the 2019 driver as compared with 2017. I created a package that only pulled data from one table in our Oracle EBS system (MTL_SYSTEM_ITEMS_B - definition widely available) which contained 284,794 rows. The data was only pulled, no destination was created. On our SQL 2017 server (48 cores with HT, 786MB) avg pull time was 27.6 seconds for 3 runs. On our brand new SQL 2019 server (48 cores with HT, 1.5TB) avg was 77.8 seconds. This same test was ran using Oracle's oledb driver with the 2017 avg being 77.8 and 2019 being 38.1. So the newer, bigger, faster server did improve Oracle's oledb pull time.
Note that there was no configuration, this was a simple drag and drop comparison. We are seeing similar results on our full upgraded package.
Edit:
This seems to be a fix: https://developercommunity.visualstudio.com/content/problem/659607/microsoft-connector-for-oracle-for-sql-server-2019.html
Taken from comment:
The solution to the performance issue is to append ArraySize to the connection string:
SERVER=*******:*****/*****;USERNAME=*********;ORACLEHOME=;ORACLEHOME64=;WINAUTH=0;ArraySize=1000000;
You can test which number is ideal for your situation.
