Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 5 of 5 total |
TClientdataset very slow. How to increase it ? |
Tue, Sep 25 2007 9:53 PM | Permanent 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 AM | Permanent 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 PM | Permanent 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 AM | Permanent 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 PM | Permanent 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 |
This web page was last updated on Tuesday, May 7, 2024 at 06:25 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |