Subject | Re: [firebird-support] Slow response on a big database? |
---|---|
Author | Anderson Farias |
Post date | 2009-02-16T17:52:03Z |
Hi,
side
IBQuery+DataSetProvider+ClientDataSet.
ClientDataSets can be easilly sorted (and very fast) so.. you can avoid
using ORDER BY that may slow some of your queries down.
The good thing about this ClientDataSet aproach (among other things) is that
if done correctly you won't have problems with long running transactions.
sure you have a good WHERE so you don't refresh tousands of records each 10
sec or so.
handling than you'll be fine!
Regards,
Anderson Farias
> I dont used JOIN SQL statement, but i use related table withDON'T. Where you can use SQL JOIN instead of "linking" datasets on client
> IBCLIENTDATASET from Delphi.
side
>but i used WHERE and ORDER BY SQL Statment at my IBCLIENTDATASET.you should no use IBClientDataSet this is a droped component. Use
IBQuery+DataSetProvider+ClientDataSet.
ClientDataSets can be easilly sorted (and very fast) so.. you can avoid
using ORDER BY that may slow some of your queries down.
The good thing about this ClientDataSet aproach (among other things) is that
if done correctly you won't have problems with long running transactions.
> 5 table always open, and 4 table open/close.This thing of frequently "refreshes" of data must be done carefully. Make
sure you have a good WHERE so you don't refresh tousands of records each 10
sec or so.
> for next Project Application, must be run/use/handle for 80 client at 18If you take care of your queries ("where" clauses, etc) and your transaction
> floor.
> so confused if my applicati9on can not handled..
handling than you'll be fine!
Regards,
Anderson Farias