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
- 10.5K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 473 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 478 Datasets
- 205 Visualize
- 256 Beast Mode
- 2.1K Charting
- 12 Variables
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 247 Distribute
- 63 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 182 Product Ideas
- 1.2K Ideas Exchange
- 12 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive