Re: TDataSetProvider: to use or not to use?
- From: Brian Bushay TeamB <BBushay@xxxxxxxxx>
- Date: Wed, 28 Sep 2005 22:23:39 -0500
>I am acessing a SQL Server 2000 Database with Delphi 7. Some of the tables
>to be read have few lines of data while others have more than 300,000
>registers. A two layer system architecture is being used.
>
>I have come through a couple of ways of retrieving this information:
>
> 1st TADODataSet (CursorType = ctOpenForwardOnly; CursorLocation =
>clUseServer)
> TDataSetProvider;
> TClientDataSet;
> TDataSource
>
> or
>
> 2nd TADODataSet (CursorType = ctStatic; CursorLocation = clUseClient)
> TDataSource
>
>Which benefits each approach will give me?
Delphi andTclientDatasets are much easier to use in an application where you
need a remote client
TadoDataset gives you better integration with SQL server and Access
>Is there a standard solution?
If there was a standard solution then you would not have two optoins
>Which
>alternative consumes less resources from the SQL Server?
TadoDataset will do a bit better here since Update/insert sql generation is
handled in the ADO layer where with TclientDataset its handled in the delphi
code for Tprovider.
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- References:
- TDataSetProvider: to use or not to use?
- From: Emile Petrus Abi-Abib
- TDataSetProvider: to use or not to use?
- Prev by Date: Re: D2005 ADO problem: multiple-step OLE DB operation generated errors
- Next by Date: Re: MS Jet Engine 4
- Previous by thread: TDataSetProvider: to use or not to use?
- Next by thread: TADOClientDataset?
- Index(es):
Relevant Pages
|
|
