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.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 600 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 687 Beast Mode
- 43 App Studio
- 38 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 385 Distribute
- 110 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 112 Manage
- 109 Governance & Security
- 8 Domo University
- 25 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive