I am currently experiencing regular time outs when requesting salesorders from SQL database:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This happens with orders that are still "in use". Trying to request orders that are in use results in the time outs.
This could be prevented if the oData request generates a SQL query with "WITH (NOLOCK)", but this doesn't seem to be the case.
In the documentation I see examples where the queries are generated "WITH (NOLOCK)":
But if check the Endpoint logs I don't see any "WITH (NOLOCK)" in the queries:
url: /orders?$filter=ordernr eq '22305480'
Connecting time: 4 ms
Executing: SELECT t.ID, t.ordernr, t.debnr, t.fakdebnr, t.verzdebnr, t.naldebnr, t.einddebnr, t.refer, t.refer1, t.refer2, t.refer3, t.orddat, t.afldat, t.afl_week, t.ordbv_afdr, t.magcode, t.selcode, t.ex_artcode,
FROM dbrkrg AS t WHERE (t.ordernr = '22305480'), time: 2 ms
Why are these not generated with "WITH (NOLOCK)"? How can I enforce this?