Re: convert LF's to SQL - LF's have Select/Omit

On 16 Apr 2013 12:17, Gqcy wrote:

On 4/16/2013 2:02 PM, rob@xxxxxxxxx wrote:

There's two view points on this:
One: I just want to convert my DDS to DDL.
Two: I am willing to go the next level to get the best
performance.

I want to protect the business by keeping current applications
functioning, i.e. Format Level Identifier is the same.

I want to be able to take advantage of the 64K page sizes, and
any other improvements in types of indexes.

The CRTLF has a PAGESIZE() parameter [and so too CRTPF if one were to create a keyed PF] so the DDS LF RcdFmt can remain unchanged. In fact done properly, the LF can be switched out without any time for the new index build; having the access path built previously, to be shared upon re-creation, then the other previously created LF deleted.

The SQL LF will be able to replace a DDS LF in some set of cases [using RCDFMT and mostly only using ADD ALL COLUMNS] while keeping the same level identifier; i.e. the ordering of columns is limited if any mapping\casting is done. Just another reason to avoid general attempts at conversions; i.e. conversions best only when there is a specific advantage to be gained. Know and understand specifically whatever are those /other improvements/ that are being sought before trying, and do not overlook that the improvements may be available to the DDS; e.g. as with PAGESIZE.