Hello

Using D2009 with edb 2.03b12.

I try to generate a rave report that include 2 edbquery with m/d relations.
It's take about 6 minutes to generate and preview this report.
On the bde version it's take about 5 seconds.

The only difference between the edb and bde version are the components i'm
using.
With bde I use RvQueryConnection and with edb RvDatasetConnection since i
remember reading somewhere that this is
the only component that work with edb.

Any suggestion what to check?
Sorin

Sorin,

<< I try to generate a rave report that include 2 edbquery with m/d
relations. It's take about 6 minutes to generate and preview this report. On
the bde version it's take about 5 seconds.

The only difference between the edb and bde version are the components i'm
using.With bde I use RvQueryConnection and with edb RvDatasetConnection
since i remember reading somewhere that this is the only component that work
with edb. >>

Are you running this with a local or remote session ?  If local, is this
running across a network with file-sharing ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote
> Are you running this with a local or remote session ?  If local, is this
> running across a network with file-sharing ?

On local session on the same pc with Win XP os.
I didn't try across network.

Thanks
Sorin

Sorin,

<< On local session on the same pc with Win XP os. I didn't try across
network. >>

If that's the case, then I would check the execution plans for the queries
and make sure that they are all optimized properly.  It sounds like the
detail query is not optimized properly, or is not parameterized properly and
is, therefore, opening and closing the tables for every single execution.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> If that's the case, then I would check the execution plans for the queries
> and make sure that they are all optimized properly.  It sounds like the
> detail query is not optimized properly, or is not parameterized properly
> and is, therefore, opening and closing the tables for every single
> execution.

Thanks

I check and the plan show the the querys are optimized already.
Also when I open the m/d querys on 2 dbgrids it's open fast.
The parameters for m/d relation is controled by Rave and this can cause a
speed decline
but still it's much more slower then with the bde.

And again the differences between the two vesion is the fact the bde use the
RvQueryConnection
and edb RvDatasetConnection.
Can this be a reason?

Thanks
Sorin

FWIW, I have used RaveReports with EDB quite a bit.  I used the
RvDataSetConnection hooked to both TEDBTables and to TEDBQueries with no
problem.  I never worried about execution plans, but then again most of the
reports were small.  I have since switched to ReportBuilder and it is MUCH
faster (or at least it APPEARS faster because it displays the first page in
the preview before it finishes generating the rest of the report).

I would suggest making sure the indexes on the tables (or queries) reflect
the sorting and joins.  I'm sure you already have, but it's possible the
dbGrids only show a subset of the data and get more records if you page
down--which may be a false representation of their higher speed.

--
David Cornelius
Cornelius Concepts

"Sorin H" <sorinh@zahav.net.il> wrote in message
news:4C26198A-9956-4469-951D-20C9BF322220@news.elevatesoft.com...
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
>> If that's the case, then I would check the execution plans for the
>> queries and make sure that they are all optimized properly.  It sounds
>> like the detail query is not optimized properly, or is not parameterized
>> properly and is, therefore, opening and closing the tables for every
>> single execution.
>
> Thanks
>
> I check and the plan show the the querys are optimized already.
> Also when I open the m/d querys on 2 dbgrids it's open fast.
> The parameters for m/d relation is controled by Rave and this can cause a
> speed decline
> but still it's much more slower then with the bde.
>
> And again the differences between the two vesion is the fact the bde use
> the RvQueryConnection
> and edb RvDatasetConnection.
> Can this be a reason?
>
> Thanks
> Sorin
>

Sorin,

<< check and the plan show the the querys are optimized already. Also when I
open the m/d querys on 2 dbgrids it's open fast. The parameters for m/d
relation is controled by Rave and this can cause a speed decline but still
it's much more slower then with the bde.

And again the differences between the two vesion is the fact the bde use the
RvQueryConnection and edb RvDatasetConnection. Can this be a reason? >>

It's certainly possible, but the normal TDataSet connection should work fine
in most cases.

Can you send me an example of the slowdown in a test application ?  I can
profile it here and see where the issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com