Share
Report
20I have been fighting with Microsoft support regarding a Dataverse timeout for Dynamics CRM online.
We have one table where requests to the API causes a timeout:
{"error":{"code":"0x80044151","message":" Sql error: SQL timeout expired. CRM ErrorCode: -2147204783 Sql ErrorCode: -2146232060 Sql Number: -2"}}
The table is not particularly big(211 columns and 9763 rows).
So far I have been fobbed off by Microsoft support about the table being too large, the number of columns being too many, the number of rows trying to be returned is too many (although the API has self-limited pagination of 5000 rows at a time) and may a column has "too huge a data to be returned"
The latest is that they are saying that "It is best and an optimal practice to split the multiple entities into various column sets rather than calling all the columns together"
Quite how this can be best and optimal to need the client to make multiple requests, for different set of columns, then stitch it back together is beyond me.
It seems that Microsoft support don't want to escalate this issue to central Microsoft (support is handled by external companies). If this was on-prem I'd simply increase the timeout from the pre-determined 2 minutes (I think) and the problem would go away.
Is there a way I can force that this issue is escalated to central Microsoft and/or get the timeout increased for the underlying database for a SaaS service?
All responses (
Answers (
