Hi,
Tested again with FB 2.5.1 & FB 2.5.5, apparently, this is not a problem from
FB 3.0, but it was already appeared since FB 2.5.
Same machine, database, query & engine, SC FB 2.5.1 & SC FB 2.5.2 runs a lot
faster than FB 2.5.5 & FB 3.0.
Regards,
Anton
01.05.2016 19:49, trsk...@yahoo.com wrote:
>
> This is the Query plan from SS FB 3.0
>
> PLAN (GET_STCK NATURAL)
This is just a different output for select from procedure GET_STCK, v3.0
does not show all its internals as v2.5 did.
You'd better compare per table performance counters (indexed/non-
Hi,
> This is the Query plan from SS FB 3.0
>
> PLAN (GET_STCK NATURAL)
>
> and here is the Query plan from SC FB 2.5.2
>
> PLAN (G_T3 NATURAL)(M_TT INDEX (RDB$PRIMARY2))(A INDEX (IDX_M_GD3))(A
> INDEX (IDX_M_GD3))SORT (JOIN (B INDEX (TM_D), A INDEX (T2_T1), C INDEX
> (RDB$PRIMARY25), D INDEX (RDB
Hi,
This is the Query plan from SS FB 3.0
PLAN (GET_STCK NATURAL)
and here is the Query plan from SC FB 2.5.2
PLAN (G_T3 NATURAL)(M_TT INDEX (RDB$PRIMARY2))(A INDEX (IDX_M_GD3))(A INDEX
(IDX_M_GD3))SORT (JOIN (B INDEX (TM_D), A INDEX (T2_T1), C INDEX
(RDB$PRIMARY25), D INDEX (RDB$PRIMARY21),
Hi,
About Db cache, found the problem. Now I could set Db Cache per database at 2
GB (16384 x 131072), try to set at 4GB (16384 x 262144), no error on gfix, but
it just crashed when tried to connect, no error message shown.
Regards,
Anto.
