Forum Discussion
Dataverse connection error : DataSource.Error: Microsoft SQL: Error code 8657
Hi @masterelaichi ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
Hi, while I still haven't been to get to the bottom of the issue I employed a work around which seems to have fixed it
What I am trying to understand is why a report that has been working fine for a more than year suddenly broke and triggered that error message. Will try and raise a support ticket if possible
I will keep an eye on this but this issue can be marked as solved (might have to come back to it if needed )
Hi masterelaichi,
The error number answers most of that. 8657 isn't a connection problem at all. It's the SQL engine refusing a memory grant: "Could not get the memory grant of N KB because it exceeds the maximum configuration limit in workload group and resource pool". So your credentials and the endpoint were never the issue. The query asked for more memory up front than the per query ceiling allows and got turned down before it ran.
That's also why it turned up out of nowhere after a year. The grant is sized from the plan's estimate, which is roughly the estimated row width times the estimated row count. Select every column from a wide entity and that number only travels in one direction as the table grows. Nothing has to change on your side for it to cross the line one day.
It's the same reason KNP's suggestion worked. Fewer columns is a narrower row, which is a smaller grant. The ones that cost you most are the long text and multiline fields, so if you want the fix to hold, drop those first rather than trimming evenly across the board.
Worth knowing before you raise the ticket. Those limits belong to the managed endpoint, so there's no setting on your side to raise. If the table keeps growing this comes back, and the durable answer is a narrower column list or splitting the pull rather than a support case.
Roughly how many columns does that entity have?
