And I forget to add call stack, architecture is super server, no changes
in config after installation.
ntoskrnl.exe!KeSynchronizeExecution+0x5b76
ntoskrnl.exe!KeWaitForSingleObject+0x1c2d
ntoskrnl.exe!KeWaitForSingleObject+0xab4
ntoskrnl.exe!KeWaitForSingleObject+0x255
ntoskrnl.exe!KeTestAlertTh
Hi all,
I have a dump file for this situations (160MB):
RESTOREFB3 Sat Jan 25 18:33:19 2020
Shutting down the server with 11 active connection(s) to 1
database(s), 0 active service(s)
RESTOREFB3 Sat Jan 25 18:33:29 2020
JProvider::shutdown:
Firebird shutdown is still in pr
Hi HTH,
thanks for the detailed explainations.
I "inherited" the sql code but updated the firebird version. And was
wondering what was ruining the performance.
Basically I want the set of first 10 entries but without 2 with a special
property.
I will just query the first 10 then and remove the
25.01.2020 07:59, Matthias Winkler spmm...@gmail.com [firebird-support] wrote:
> The major problem is, that with firebird 2.1.3 the query also completes
> within 3 seconds.
> Something seems to have changed with the optimizer, execution plan or
> whatever (~ sorry I
> dont know the terms here)
>
As Karol writes, introducing a descending index on the ID field ought to
make your query quick (Firebird indices - and keys - are unidirectional).
Firebird has never been good with IN(), I was bitten around
1999, changed to using EXISTS and for the last 20 years I have never
missed IN() (and N
