Issue
Performance issues and/or connection timeouts occurring in workflows that pull data from Redshift using the Simba Redshift ODBC Driver
Environment Details
- Alteryx Designer, Server (enter product name as appropriate)
- Simba Redshift ODBC Driver
Cause
The driver might be configured to use up all of the system memory before writing data to the workflow. This can work normally for smaller amounts of data but past a certain point it will run out of memory and that's where performance issues really start to take effect.
Resolution
The crucial setting is found in the ODBC DSN configuration in ODBC Data Sources (64-bit). Edit the DSN and go to
Additional Options. The setting that can lead to performance issues is
Retrieve Entire Result Into Memory. Changing this setting to
Single Row Mode or
Declare/Fetch with a set
Cache Size can improve performance on some machines and should be tested in troubleshooting Redshift connection performance.

Additional Resources