flowable / flowable/flowable-engine
Sql performance in MS SQL when paging
Open
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 7h 8m
- Merged PRs (30d)
- 2
Description
We have some performance problems on our Flowable Installation especially when paging big datasets.
Is there any reason to not use "OFFSET xxx ROWS FETCH NEXT xxx ROWS ONLY" syntax as for mysql?
The Offset syntax requires a order by clause before. I was looking quickly throw the different queries and it seems to be there every time, it wouldn't be very clean to not use an order by in paging.
If you agree i could create a Pull Request with the different mssql.properties file.
Thanks
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.