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
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 309 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 663 Datasets
- 119 SQL DataFlows
- 2.3K Magic ETL
- 823 Beast Mode
- Visualize
- 2.6K Charting
- 86 App Studio
- 46 Variables
- Automate
- 193 Apps
- 483 APIs & Domo Developer
- 87 Workflows
- 23 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 117 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 143 Governance & Security
- 11 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 116 Community Announcements
- 5K Archive