Subject | Re: [firebird-support] BLOB performance |
---|---|
Author | Ann W. Harrison |
Post date | 2005-01-21T16:18:12Z |
yuraukar wrote:
the database. When you retrieve the record, the "normal" fields you
request are returned. If you include the blob field, you get a number
that tells the system where to find the blob. You then go back and get
the blob if it exists. So blobs don't slow down "normal" fields. Going
back to get the blob is cheaper than opening a second table - let alone
opening a second file.
Regards,
Ann
>Don't be. It's OK.
>
> Similar to my varchar question: I am concerned about BLOB performance.
> Someone indicated that tables having a BLOB field perform slower. InSomeone was wrong. That happens.
> fact, the statement was that the whole DB would/could perform slower
> if using a single fdb/gdb file.
> Is that true? Would I be better off moving the BLOB field into aNo. Blobs are not part of the record, but are stored on data pages in
> separate table or even file?
the database. When you retrieve the record, the "normal" fields you
request are returned. If you include the blob field, you get a number
that tells the system where to find the blob. You then go back and get
the blob if it exists. So blobs don't slow down "normal" fields. Going
back to get the blob is cheaper than opening a second table - let alone
opening a second file.
> I have the situation where a table has some "normal" columns whichUse a blob field in the relevant record.
> will always be filled and only in some rare situations, additional
> BLOB data will need to be attached. What would be the best design here?
Regards,
Ann