Hi all,
Just migrating from SC FB 2.5.2 to SS FB 3.0 (both in Win x64), i found a few
problems :
1) Query that runs about 2-3 secs in SC FB 2.5.2, runs minutes in SS FB 3.0
Query is something like this :
Select a.col1,b.col1 from tbl1 a, tbl2 b where a.id = b.id and b.id in (select
c.id from
FB 2.14 - Delphi 2007 - IBDAC TIBCScript
Although I'm certain this is not a Delphi problem, I've included a copy of the
commands used to create the SQL. Those commands work in FlameRobin, and in
IBExpert. I used both to create working DDL, which I copied into my delphi
program. Any help or
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
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
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,
1. will be good to see this query plans
2. will be good to see exact error message
3. also check your db by gfix –validate –full
regards,
Karol Bieniaszewski
From: mailto:firebird-support@yahoogroups.com
Sent: Sunday, May 1, 2016 8:35 AM
To: firebird-support@yahoogroups.com
Subject:
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.
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