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.)

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.