Issue Summary

Customers are frequently going through all the stories/features/epics using skip and top from the first page of data to the last with no filter, so nowhere clause, so all rows. When the skip value becomes large, this causes the performance of SQL Server queries to become very slow and triggers performance warnings.

Steps to Reproduce

Sample queries:

/rest/align/api/2/stories?$select=lastUpdatedDate,title,id&$orderBy=lastUpdatedDate desc&$top=100&$skip=48000 

/rest/align/api/2/epics?top=5&skip=1010

Expected Results

To be able to retrieve the results.

Actual Results

Those requests are usually timeout both at the client and the server sides.

For example, this request was completed in 119secs on the server-side but got "504 Gateway Timeout" on the client-side.

2022-04-14 08:24:49 xxx.xxx.xxx.xxx GET /rest/align/api/2/epics top=5&skip=1015 443 - xxx.xxx.xxx.xxx PostmanRuntime/7.29.0 - 200 0 64 119028

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.
NOTE: Sometimes it is helpful to reduce the desired dataset range/amount. However, customers who start to experience this problem get an error after a while even when they try to pull very little data.