×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We have an SQL statement that occasionally runs really slowly (up to 120
seconds). When I run the statement interactively in debug mode, the
joblog shows a recommendation that a permanent access path is built as
that may help the query run faster.
The SQL runs over a logical file that is keyed on account number plus
another five sub-keys and only contains records with the open amount
field set to zero. The logical file is joined to the physical file
using a left outer join and relative record numbers (amongst other
criteria) and the resulting data is sequenced to match the sequence from
the logical file.
The suggestion though, says to create a permanent access path for the
logical file and then says to base it over the physical. The question I
have though is how do you create a permanent access path?
From reading various references, I got the impression that this meant
use the CREATE INDEX statement, but that just creates a logical file and
as the logical file I want already exists it doesn't seem to make much
sense to create another one.
Thanks
Jonathan
_______________________________________________________
This message was sent using NOCC v1.14 webmail software
_______________________________________________________
midrange.com
