Performance of UNION in RedShift
Has anyone used UNION successfully with RedShift in DOMO? I have a DF that seems to stall on the query using the UNION. I don't know if it would error out b/c I'm too impatient (after waiting 30 m), but I ended up revising how I wrote the script to not need the UNION...but was curious why it would have been delayed SOOOO long...300k rows unioning on 300 rows....
Thanks and have a great day.
Best Answer
-
If you're not worried about removing duplicates, then UNION ALLshould skip the DISTINCT step of the UNION operation and improve your performance a bit.
2
Answers
-
If you're not worried about removing duplicates, then UNION ALLshould skip the DISTINCT step of the UNION operation and improve your performance a bit.
2 -
I just introduced my palm to my head after I read that. I did leave off ALL. Crap. Thanks for chiming in and helping me out. Good catch! I should have used UNION ALL but left it out.
1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive