× 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.



My understanding was that I needed DDS Logicals to get the same format level id.
It appears that with 6.1 that isn't the case, in that DDL (SQL) defined files will have the same format id as the DDS physicals and logicals.

I have tested the "GENDDL" tool, and have proven that it will generate the SQL that matches the fmt ID of the DDS files. So this means that I don't have to create logical files out of my old physicals.

-gerald






rob@xxxxxxxxx wrote:
Not sure about this:
<snip>
I will create new SQL indexes prior to re-creating my old logicals.
what else can/should I do to my logicals?
</snip>
Were you thinking about recreating your logicals in DDS, but first create indexes? I do not see a reason to use DDS to recreate your logicals.

Some indexes you may not have but which may come in handy ...
If you have select/omit logicals (which you can do just fine in DDS on 6.1) like this
CREATE INDEX ROB/gqcyl1
ON ROB/GQCY (MUVALUE) WHERE RECID='A'
Then you may also want an index like this first
CREATE INDEX ROB/gqcyl2
ON ROB/GQCY (recid, MUVALUE)
I think this will help performance of queries over the base table which do something like
SELECT ...
FROM GQCY
WHERE RECID='A'...
And I think you want those created first.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.