Users working with reports occasionally encounter the error “Query exceeded memory limit.”
However, report creators have no way to determine which specific query caused the memory limit to be exceeded.
It would be helpful to have a feature, such as in Fabric Capacity Metrics, to identify which queries caused the memory limit to be exceeded.
No CommentsBe the first to comment
Recent ideas
Add "Add to Dictionary" and "Ignore All" Functionality to Power BI Text Boxes
When creating professional Power BI reports, legitimate company names, project names, industry-specific terms and technical terminology are sometimes incorrectly flagged as spelling errors with a red...mmartelozzo3 hours agoNew MemberNew3Views0likes0CommentsFix Direct Lake semantic model binding in Deployment Pipelines
When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials....lk12312 hours agoAdvocate INew1.5KViews27likes2Comments:: operator for typecast in T-SQL
Introduce support for the ::type cast operator in Fabric Data Warehouse as syntactic sugar for the existing CAST(... AS type) expression. The new operator would be functionally equivalent and compile...jovanpop-msft14 hours agoMicrosoft EmployeeNew47Views7likes2CommentsAllow calls of Fabric SQL Database stored procedures from Data Warehouse
It would be great if there were a possibility to call a SQL Database stored procedures directly from a Data Warehouse stored procedures. A use case for this would be e.g. logging activities and even...Vojtech_Dolejsi17 hours agoNew MemberUnder Review2.9KViews13likes2Comments