Federated Queries - Dynamic SQL Generation Improvements
Options
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
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 556 Datasets
- 2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 570 Beast Mode
- 11 App Studio
- 27 Variables
- 579 Automate
- 141 Apps
- 414 APIs & Domo Developer
- 23 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 351 Distribute
- 91 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 92 Manage
- 89 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 85 Community Announcements
- 4.8K Archive