Hey Stan,
A LOB will not be buffered. This means that you can make the bufferpool as
big or as small as you want, it would not make any difference for your BLOB
(it will offcourse for the other data in your table).
The space requirements will really depend on how much you will store into
this table. However, you can put the LOB into it's own tablespace.
Personally I would prefer this since this can help later on should you want
to move to raw devices or tune filesystems for direct IO (not to use
buffering). You can then leave the LOB tablespace on a buffered filesystem
to help performance (since LOB's do not get logged).
Thanks.
"Stanley Sinclair" <st************ *@bellsouth.net > wrote in message
news:6f******** *************** ***@posting.goo gle.com...
(Minor question. Since updating to FP4 I cannot access HTML help.
Compiler error. What's wrong?)
_______________ ________
Subject of this message:
There is lots of Help regarding getting data out of BLOB and CLOB
storage, but I see little on getting data into it. I know it's there,
but could someone speed my search? A colleague created the following
table:
CREATE TABLE BLOB_TABLE (
BLOB_ID INT NOT NULL GENERATED ALWAYS AS IDENTITY...,
BLOB_IMAGE BLOB,
BLOB_NAME VARCHAR(100),
BLOB_TYPE VARCHAR(10),
PRIMARY KEY (BLOB_ID)
)
I'm wondering how large the bufferpool and tablespace has to be? Is
this where the BLOB_IMAGE should be placed?
Stan