Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Thanks in advance for any support you can provide.
Working with Microsoft support, I was able to determine that the size of a query/column is preventing my table from being refreshed via an onsite gateway. The body of the message from the product team is below:
we see one of the packet with the size over 8MB has been blocking the process here, which in turn means one of the column has the arbitrary value over the threshold which is causing the issue.
10768a89-4e2a-4f61-bed2-a9119c436b87 C146AA94 [DM.Relay] Not compressing or shrinking 9367921 bytes compressed with Level6
cb01fec9-1267-41e3-a1b0-711bf8b82e64 48AAEF35 [DM.GatewayCore] Executing query (timeout=7124) "<pi>SELECT * FROM [Query1]</pi>", requestId=null
could you please check The aforementioned exception present in which query or the column is producing huge sized packet, we would suggest you to try modifying the query accordingly or delete the column which is the cause here and try the refresh again.
My question is how can I identify which querry is causing the 8MB process? Is there a function or utlity within BI that can identify the memory need for the request? My file updates on the desktop version of BI and only has the error when refreshing via the server.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
112 | |
100 | |
76 | |
74 | |
49 |
User | Count |
---|---|
146 | |
108 | |
106 | |
90 | |
62 |