I will try to give some tips to help you improve your package performance. You should start troubleshooting your package systematically to find the performance bottleneck.
Some provided links are related to SQL Server. No worries! The same rules are applied in all database management systems.
1. Available resources
First, you should ensure that you have sufficient resources to load the data from the source server into the destination server.
Ensure that the available memory on the source, ETL, and destination servers can handle the amount of data you are trying to load. Besides, make sure that your network connection bandwidth is not decreasing the data transfer performance.
Make sure that the following hardware issues are not occurring in any of the servers:
- Drive out of storage
- Server is out of memory
Make sure that your machine is not running out of memory. You can simply use the Task Manager to identify the amount of available memory.
2. The Data Source
Make sure that the table is not a heap
After checking the available resources, you should ensure that your data source is not a heap. At least it would be best if you had a primary key created on that table.
Indexes
If your SQL Command contains any filtering, ordering, or Joins, you should create the indexes needed by those operations.
OLE DB provider
Instead of using OLE DB source to connect to Oracle, try using the Microsoft Connector for Oracle (Previously known as Attunity connectors). Microsoft previously mentioned that it should provide faster performance than traditional OLE DB providers.
Use the Oracle connection manager rather than OLE DB connection manager.
To be honest, I am not sure if this component can make the data load faster since I didn't test it before
Removing the destination and adding a dummy task
The last thing to try is to remove the ODBC destination and add any dummy task. For example, use a row count component.
Run the package; if the data is loaded faster, then loading data from Oracle is not decreasing the performance.
3. SSIS configuration
Now, let us start troubleshooting the SSIS package.
Running in 64-bit mode
First, try to execute the package in 64-bit mode. You can change this from the package configuration. Make sure that the Run64bitRuntime property is set to True.
Data flow task buffer size/limits
Using SSIS, data is loaded in memory while being transferred from source to destination. There are two properties in the data flow task that specifies how much data is transferred in memory buffers used by the SSIS pipelines.
Based on the following Integration Services performance tuning white paper:
DefaultMaxBufferRows – DefaultMaxBufferRows is a configurable setting of the SSIS Data Flow task that is automatically set at 10,000 records. SSIS multiplies the Estimated Row Size by the DefaultMaxBufferRows to get a rough sense of your dataset size per 10,000 records. You should not configure this setting without understanding how it relates to DefaultMaxBufferSize.
DefaultMaxBufferSize – DefaultMaxBufferSize is another configurable setting of the SSIS Data Flow task. The DefaultMaxBufferSize is automatically set to 10 MB by default. As you configure this setting, keep in mind that its upper bound is constrained by an internal SSIS parameter called MaxBufferSize which is set to 100 MB and can not be changed.
You should try to change those values and test your package performance each time you change them until the package performance increases.
4. Destination
Indexes/Triggers/Constraints
You should make sure that the destination table does not have any constraints or triggers since they significantly decrease the data load performance; each batch inserted should be validated or preprocessed before storing it.
Besides, the more you have indexes the lower is the data load performance.
ODBC Destination custom properties
ODBC destination has several custom properties that can affect the data load performance such as BatchSize (Rows per batch), TransactionSize (TransactionSize is only available in the advanced editor).
