I’ve successfully reproduced the issue you reported. After thorough investigation, I’ve identified two key factors contributing to the problem:
JSON Column Size Limit:
It appears that the JSON columns in your table need to be adjusted. Currently, the size limit for each record is reaching the threshold, and I recommend reducing the size of your JSON columns in the StockMRQEvaluationData table. Ideally, aim for a maximum of 64 kB per record to ensure optimal performance. In the feature, we will block the applications that exceed the limit.
Indexing for Sorting:
The issue you’re encountering is related to the sorting operation by the created column. To enhance the sorting efficiency, it’s crucial to add an index for the created column in the StockMRQEvaluationData table. This index will significantly improve the query performance and resolve the sorting-related challenges.
By addressing these two aspects, you should observe a noticeable improvement in the system’s behavior and resolve the reported issue effectively.
thank you for the effort to investigate the problem. The indexing did the trick.
But, with regards to the 64 kB threshold and the potential blocking of my application. This would mean a redesign of a major part of the application and the front end. For that reason it would be helpful to identify the most critical columns.