Subquery versus Output Table
I am always looking to optimize my dataflows and was curious if it was better to have multiple output tables in a dataflow or less output tables by utilizing subqueries? For debugging and readability it is nice to have multiple output tables but I do not want to do this if it will have a negative impact on performance.
Thanks in advance for your responses.
-----------------
Chris
Best Answer
-
hey @cwolman!
For larger datasets at least, having multiple transforms is a good way to go, in my experience subqueries seem to bog down a bit for the larger sizes.
For smaller datasets, do it either way, whatever works best for you.
Seems like you're on the right track!
**Say 'Thanks' by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem as 'Accepted Solution'1
Answers
-
hey @cwolman!
For larger datasets at least, having multiple transforms is a good way to go, in my experience subqueries seem to bog down a bit for the larger sizes.
For smaller datasets, do it either way, whatever works best for you.
Seems like you're on the right track!
**Say 'Thanks' by clicking the thumbs up in the post that helped you.
**Please mark the post that solves your problem as 'Accepted Solution'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
- 101 SQL DataFlows
- 622 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 748 Beast Mode
- 59 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 396 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 125 Manage
- 122 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 109 Community Announcements
- 4.8K Archive