Hi,
I started this thread, and it's evolution has lead me to believe that in
fact I may not understand the implementation of the BLOCKFACTOR attribute.
The following is from the 4.5 Studio help:
BLOCKFACTOR
Optional. Specifies the maximum number of rows to fetch at a time from the
server. The range is 1 (default) to 100. This parameter applies to ORACLE
native database drivers and to ODBC drivers. Certain ODBC drivers may
dynamically reduce the block factor at runtime.
My understanding of this is that it determines the number of rows to fetch,
regardless of size. Am I wrong?
Also, are you able to answer my other question about if or not the MAXROWS
would take precedence and if a stored procedure was used, what effect
BLOCKFACTOR and MAXROWS have if the SP itself was limiting rows.
Thanks a bunch,
James
----- Original Message -----
From: "Dave Watts" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 20, 2000 2:51 PM
Subject: RE: BLOCKFACTOR and MAXROWS
> > > > I assume this means you don't set BLOCKFACTOR in those cases
> > > > where doing so would slow CF down. (That is, those cases where
> > > > the data returned exceeds 32K.)
> > >
> > > There's nothing wrong with using BLOCKFACTOR when you're
> > > returning datasets larger than 32Kb. In fact, that's the best
> > > time to use it. What you don't want to do, according to the
> > > folks at Allaire, is use a value for BLOCKFACTOR which would
> > > end up being larger than 32Kb. So, you find out the maximum
> > > length of a single row in Kb, and divide that into 32Kb.
> >
> > I think/hope we're saying the same thing.
> >
> > Re-writing your sentence below to state it to my understanding:
> >
> > "What you don't want to do, according to the folks at Allaire,
> > is use a value for BLOCKFACTOR, where BLOCKFACTOR multiplied by
> > the row size exceeds 32Kb."
>
> I'm not sure if we're saying the same thing or not. Looks to me like your
> chad is hanging.
>
> Seriously, though, what I'm saying is that you don't want to set the
> BLOCKFACTOR attribute to a value higher than the maximum length of a
single
> row, divided into 32Kb. That's almost always going to give you a value
> greater than 1, however, so you'd get some value out of setting it to the
> appropriate size.
>
> > I also thought BLOCKFACTOR had a maximum value of 100.
>
> So I've been told, although I haven't checked for myself. It's relatively
> rare that you'd be able to set it this high, anyway - you'd need pretty
> short rows for that.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> voice: (202) 797-5496
> fax: (202) 797-5444
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
