Troubleshooting: Slow Data Loader With Subquery Columns
Subquery columns often generate correlated SQL that runs repeatedly for each row in the staging table. Runtime increases when:
- More rows match the subquery condition.
- Related tables grow in size.
- Subqueries depend on SQL columns that can't be indexed.
- Downstream join tables build on a slow base table.
Select the
Bypass Data Import
check box on the slow data loader.- Identify the slow loader in the task log.
- SelectIntegrationsfrom the main menu.
- SelectDesign Integrations.
- Select your task in theComponent Library.
- SelectLogsin theActionspanel.
- Identify the slow data loader based on the logs.
- Select theBypass Data Importcheck box.
- Select the slow data loader in theComponent Library.
- SelectPreview loader outputin theActionspanel.
- Select theBypass Data Importcheck box.
- SelectPreview loader output.
Identify and refactor the slow staging table.
If the issue remains after you use the
Bypass Data Import
check box, open the staging table and time the Preview Data process to find the slow base table to refactor.- Select the target data source for the slow data loader in theComponent Library.
- Select the target staging table.If the target table is a join or union table, trace back to the first slow base table.
- SelectPreview data.
- Repeat these steps until you identify the slow table.
- After you identify the slow table, check the table for:
- Subquery columns.
- SQL columns used in joins.
- High data volume.
- Duplicate rows from a cartesian join.
- Refactor your staging table to:
- Use a join-based design.
- Filter earlier.
- Add indexes on base columns.
- Prepare data upstream.