Subject | Re: Migrating from Super Classic FB 2.5.2 to SuperServer FB 3.0 could have a problems |
---|---|
Author | Dmitry Yemanov |
Post date | 2016-05-01T18:03:01Z |
01.05.2016 19:49, trskopo@... wrote:
does not show all its internals as v2.5 did.
You'd better compare per table performance counters (indexed/non-indexed
reads) after execution.
Dmitry
>This is just a different output for select from procedure GET_STCK, v3.0
> This is the Query plan from SS FB 3.0
>
> PLAN (GET_STCK NATURAL)
does not show all its internals as v2.5 did.
You'd better compare per table performance counters (indexed/non-indexed
reads) after execution.
> This could be a big problem, all queries/stored procedures/triggers mustThis is always required when migrating to the new major version.
> be test again for its performance.
Dmitry