Tweet
Hi,
We are using CSVUtil to load data. List of tables are listed below. Our initial load takes about 2+ hrs to complete. We may have more loads to process as well. What are some of the tuning techniques for this type of data load ? Obvioulsy we dont want the PK/triggers/FK constraints disabled during the load, otherwise data integrity is compromised.
My thinking is to drop the secondary btree indexes on GLOGOWNER for these tables, load the data and then rebuild 'em. Another idea is to "group" these tables based on parent-child relationship and load 'em in parallel.
Any other thoughts ?
TIA
Mohan
SPLC
CORPORATION
LOCATION
LOCATION_CORPORATION
LOCATION_ADDRESS
LOCATION_REFNUM
LOCATION_REMARK
LOCATION_RESOURCE_TYPE
CALENDAR
LOCATION_ROLE_PROFILE
LOCATION_STATUS
LOCATION_ACTIVITY_TIME
LOCATION_ACCESSORIAL
ACTIVITY_CALENDAR
CONTACT
CONTACT_CORPORATION
CONTACT_COM_METHOD
We are using CSVUtil to load data. List of tables are listed below. Our initial load takes about 2+ hrs to complete. We may have more loads to process as well. What are some of the tuning techniques for this type of data load ? Obvioulsy we dont want the PK/triggers/FK constraints disabled during the load, otherwise data integrity is compromised.
My thinking is to drop the secondary btree indexes on GLOGOWNER for these tables, load the data and then rebuild 'em. Another idea is to "group" these tables based on parent-child relationship and load 'em in parallel.
Any other thoughts ?
TIA
Mohan
SPLC
CORPORATION
LOCATION
LOCATION_CORPORATION
LOCATION_ADDRESS
LOCATION_REFNUM
LOCATION_REMARK
LOCATION_RESOURCE_TYPE
CALENDAR
LOCATION_ROLE_PROFILE
LOCATION_STATUS
LOCATION_ACTIVITY_TIME
LOCATION_ACCESSORIAL
ACTIVITY_CALENDAR
CONTACT
CONTACT_CORPORATION
CONTACT_COM_METHOD