Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2026 03:09 PM
HI @Manas2000 ,
This appears to be a Databricks SQL MCP limitation, not a Databricks SQL warehouse limitation.
A hacky workaround might be to manually paginate in SQL, e.g., with `ROW_NUMBER()` or `LIMIT/OFFSET`, and run separate MCP calls for each page.
But candidly for large result extraction, MCP is the wrong tool. You could use the Databricks Statement Execution API directly with chunking or `EXTERNAL_LINKS`.
Hope that helps.
AI/BI Consultant | Databricks, Power BI, Genie, Metric Views, Unity Catalog
Focused on governed, business-ready analytics and practical lakehouse adoption.
Focused on governed, business-ready analytics and practical lakehouse adoption.