It's not necessary. It's supposed to be speed queries up, IF your
query qualifies. My recollection is the amount of data returned
with BLOCKFACTOR = n must be below a certain amount (32K?) If the
data exceeds this amount, I'm told CF backs up and tries n-1, n-2,
etc, which can slow things down.
I haven't been concerned about the 32K (or whatever the actual
number is) because I typically use BLOCKFACTOR = 100 to get a list
of primary keys based on the SELECT criteria. I then use the list
of primary keys to pull entire rows of data (for each value of the
primary key) out of my database stored in memory in a Structure.
best, paul
At 11:56 PM 8/22/00 -0600, you wrote:
>Reading between the lines here... Are you saying that BLOCKFACTOR
>doesn't affect the number of of rows returned in a query, it just
>affects the interaction between the ODBC driver and CF?
Yes.
> I'm not sure
>that I have any idea then if designating the BLOCKFACTOR is either
>necessary or benificial to any givent SP call.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
