Re: Specifying Maximum Length of BLOB

When defining a BLOB you can also specify ALLOCATE.  If you use ALLOCATE
then the BLOB (when less than or equal to ALLOCATE size) will be stored in
the same base record, and one I0 operation will get both.

Internally there can be work buffers allocated which, in some cases, may be
allocated based on the maximum size of the BLOB rather than the actual size
of the BLOB being referenced.  Allocating a 2GB buffer can be more resource
intensive than allocating a 100K buffer...  I would suggest trying to
define the BLOB column as up to 16MB rather than 2GB when you really don't
need it any larger.

Bruce Vining



                                                                           
             "Walden H.                                                    
             Leverich"                                                     
             <WaldenL@techsoft                                          To 
             inc.com>                  <midrange-l@xxxxxxxxxxxx>           
             Sent by:                                                   cc 
             midrange-l-bounce                                             
             s@xxxxxxxxxxxx                                        Subject 
                                       Specifying Maximum Length of BLOB   
                                                                           
             12/29/2005 02:07                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
                                                                           
                                                                           




Is there any reason to limit my blob sizes when defining a table? I refer
to technical/performance limits, not the administrative limits of
preventing people from inserting something that is "too big".

I can almost see a reason if I can keep the base row and the blob size
below 32K. Then the db _might_ be smart enough to keep the base row and the
blob on the same database page.

However, if I can't keep it below 32K then is there any reason not to
specify Blob(2G) when creating my tables?

And anyone know if the DB is smart enough to store blobs in situ with the
row if the total row is limited to 32K?

-Walden

------------
Walden H Leverich III
President & CEO
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.