Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread TClientdataset very slow. How to increase it ?
Tue, Sep 25 2007 9:53 PMPermanent Link

Davis
Hi all,

Im using the dbisam with tclientdataset. On server side use nested queries. On client
side,when the master clientdataset is openned the performance is ok, but when use the
nested dataset ( datasetfield property ) the performance go down. How to increase this
performance ?


Thanks.
Thu, Sep 27 2007 10:42 AMPermanent Link

"David Farrell-Garcia"
Davis wrote:

> Hi all,
>
> Im using the dbisam with tclientdataset. On server side use nested
> queries. On client side,when the master clientdataset is openned the
> performance is ok, but when use the nested dataset ( datasetfield
> property ) the performance go down. How to increase this performance ?
>
>
> Thanks.


Have you tried wiring up your Master-Detail ClientDatasets without
using nested datasets for performance comparision?

--
David Farrell-Garcia
Whidbey Island Software, LLC
Thu, Sep 27 2007 8:15 PMPermanent Link

Davis
Ok, using it the performance increase 1000%, but it bring all records ? Can force the
network ?


Thanks.

"David Farrell-Garcia" <davidF@NoStinkingSpamWhidbeyIslandSoftware.com> wrote:

Davis wrote:

> Hi all,
>
> Im using the dbisam with tclientdataset. On server side use nested
> queries. On client side,when the master clientdataset is openned the
> performance is ok, but when use the nested dataset ( datasetfield
> property ) the performance go down. How to increase this performance ?
>
>
> Thanks.


Have you tried wiring up your Master-Detail ClientDatasets without
using nested datasets for performance comparision?

--
David Farrell-Garcia
Whidbey Island Software, LLC
Fri, Sep 28 2007 11:27 AMPermanent Link

"David Farrell-Garcia"
Davis wrote:

> Ok, using it the performance increase 1000%, but it bring all records
> ? Can force the network ?


You don't have to bring all records, of course.  Use a paramaterized
query and build a proc to run the query each time the user either
scrolls or requests detail records. Then test that against your nested
dataset performance.

If you do not nest the datasets you lose some of the convienence of
have the detail tables open with a single open call to the master table
and you must also apply the updates to the detail records separatly but
you can wrap that all up in a single procedure.


--
David Farrell-Garcia
Whidbey Island Software, LLC
Sat, Sep 29 2007 3:48 PMPermanent Link

Davis
Thanks David,

 Im changed to master-detail datasets. Works fine.


Davis.


"David Farrell-Garcia" <davidF@NoStinkingSpamWhidbeyIslandSoftware.com> wrote:

Davis wrote:

> Ok, using it the performance increase 1000%, but it bring all records
> ? Can force the network ?


You don't have to bring all records, of course.  Use a paramaterized
query and build a proc to run the query each time the user either
scrolls or requests detail records. Then test that against your nested
dataset performance.

If you do not nest the datasets you lose some of the convienence of
have the detail tables open with a single open call to the master table
and you must also apply the updates to the detail records separatly but
you can wrap that all up in a single procedure.


--
David Farrell-Garcia
Whidbey Island Software, LLC
Image