UniQuery and UniDirectional performance
Posted: Thu 22 Apr 2010 02:18
Hi,
D2010, SQL Express 2008.
I'm used to setting UniDirectional = True when I'm getting data to iterate through without performing updates. I used to set this as a matter of course for BDE/Paraox data access in old applications which I'm now converting to UniDAC.
Using UniQuery, I thought this should also give better performance but in a simple test case I was looking at recently, setting UniDirectional to True actually slows down the loop by almost 5 times using the same query compared to when UniDirectional is false.
Can you explain this please? Are there any 'best practices' for how or when to use UniDirectional?
I see also that FetchAll must be false when unidirctional = True, this would seem to slow down the performance too.
Regards, Paul.
D2010, SQL Express 2008.
I'm used to setting UniDirectional = True when I'm getting data to iterate through without performing updates. I used to set this as a matter of course for BDE/Paraox data access in old applications which I'm now converting to UniDAC.
Using UniQuery, I thought this should also give better performance but in a simple test case I was looking at recently, setting UniDirectional to True actually slows down the loop by almost 5 times using the same query compared to when UniDirectional is false.
Can you explain this please? Are there any 'best practices' for how or when to use UniDirectional?
I see also that FetchAll must be false when unidirctional = True, this would seem to slow down the performance too.
Regards, Paul.