Changing (t_1.tr_type = '1') to t_1.tr_type = 1 increased the speed by a
few seconds.
tr_type is a Integer. Now the report is just a little bit slower than 7.5
I print this same report using several different Where statements, so now
that I am getting
close I need to start testing the other Where statements and keep tweaking.
If I make any big discoveries I will pass them on
Thanks all
Marc
--------------------------------------------------
From: "Ben Petersen" <[email protected]>
Sent: Friday, May 08, 2009 8:23 AM
To: "RBASE-L Mailing List" <[email protected]>
Subject: [RBASE-L] - Re: 7.5 vs V8 speed
Hi Marc,
I'm looking at
(t_1.tr_type = '1') AND
I don't recall -- do parens force usage of an index, or the reverse?
Regardless, you might try w/o them.
Is tr_type actually a string data type (single quotes)?
I understand that the main question is why it takes twice as long
under v8 to print the report, but one thought might be to limit the
data, either in the view or the where clause for the report.
So
WHERE +
(t_1.tr_type = '1') AND +
might become something like
WHERE +
dr_num = 1234 and +
(t_1.tr_type = '1') AND +
Assuming dr_num (or what ever limiting data) is indexed, and early in
the where clause, the report should start pretty quickly.
If the report is based off a view why
does it access the individual tables?
Someone mentioned earlier that a view is just a stored Sql Query,
there is no data stored in a view. They are also referred to as
"pseudo tables" because, just like this report, you can refer to a Sql
Query as though it is a table. Of course you can stack one view on top
of another if need be. So views are just a convenient way for
referring to/using queries.
Since selecting against this view is as fast as it was under 7.5
(that's correct??) I think the suggestions referring to settings in
the report itself make the most sense. If your view construct was
faulty I would think performance would be poor under both platforms.
Ben
