Federated Queries - Dynamic SQL Generation Improvements

DataArchitect
Member
I've observed that the dynamic SQL that gets executed for federated datasets isn't always the most optimal. For instance to fetch the possible value list for a series or quick filter, it is still executing the same query as for the main card. It would perform much faster if it did a distinct over just the column needed for that quick filter. Or it shared the results from the main card query. But I've seen Domo execute two queries that are identical, once for the main card but then a second for quick filter options. It makes the federated database work harder than it needs to. Plus if the federated DB is a columnar db such as Redshift, it could return a distinct list much faster rather waiting for the aggregate query to return.
Tagged:
1
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 310 Workbench
- 7 Cloud Amplifier
- 9 Federated
- 3K Transform
- 113 SQL DataFlows
- 651 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 792 Beast Mode
- 78 App Studio
- 44 Variables
- 754 Automate
- 187 Apps
- 479 APIs & Domo Developer
- 71 Workflows
- 17 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 407 Distribute
- 118 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 141 Manage
- 137 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive