Re: TADOStoredProc

On Thu, 11 Oct 2007 02:30:47 +0100, Brian Bushay TeamB <BBushay@xxxxxxxxx> wrote:
TAdoQuery sets the SQL using a Tstringlist while TadoDataset uses a Widestring;
While both can set the SQL in the underlying ADO dataset there is a performance penalty if you set it one line at a time like AdoQuery.sql.Add('this line');
leads you to do

But it's always worth remembering that the performance penalty for each additional CPU operation is only nanoseconds, rather than the milliseconds for each additional disk access.

I'm not saying that tAdoDataSet and tAdoCommand aren't a "better fit" to the underlying ADO architecture, just that simply replacing all tAdoQuerys and tAdoStoredProcs in an under-performing program probably /won't/ give a significant speed boost.

( But I still pre-calculate invariants and store them in local variables before every FOR loop :) )

--
Paul Scott
Information Management Systems
Macclesfield, UK.
.