Subject Re: [firebird-support] Re: Stumped on SQL Indexing/Bad Plan-ing
Author Steve Wiser
Interesting. Maybe it is slow because of the sorts with the returned blob
fields? Why don't you just make a stored procedure with a query
to return the primary keys of the tables you are interested in and inside
the for pull out the blobs and rest of the data?


Steve Wiser
Specialized Business Software
6325 Cochran Road, Unit 1
Solon, OH 44139
(440) 542-9145 - fax (440) 542-9143
Toll Free: (866) 328-4936

On Thu, Aug 11, 2011 at 11:31 AM, red_october2009 <
kevin.wendy.morris@...> wrote:

> **
> Here is some further info:
> I have been experimenting by eliminating JOINed tables, and fields that
> pull from tables in the JOIN.
> If I pull back only fields from s then the execution time is fast. As I add
> VARCHAR() fields from the JOINed tables, execution slows, but is still
> acceptable (< 2 seconds).
> However when I add BLOB SUB_TYPE 1 fields from the JOINed tables, it kills
> the response time... up to 9 seconds.
> Pulling back BLOB fields seems to be the hold up. However, I need those
> fields. Is there a way to make the blob fields in the query not so damaging
> to response time?
> This message and any files transmitted with it may contain information that
> is privileged, confidential, and exempt from disclosure under applicable
> law. They are intended solely for the use of the intended recipient. If
> you are not the intended recipient, distributing, copying, disclosing, or
> reliance on the contents of this communication is strictly prohibited. If
> this has reached you in error, kindly destroy this message and notify the
> sender immediately. Thank you for your assistance.
> We attempt to sweep harmful content (e.g. viruses) from e-mail and
> attachments, however we cannot guarantee their safety and can accept no
> liability for any resulting damage. The recipient is responsible to verify
> the safety of this message and any attachments before accepting them.

[Non-text portions of this message have been removed]