Difference between revisions of "Sql convert from dds"
As400doofus (talk | contribs) |
As400doofus (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
WORK IN PROGRESS | WORK IN PROGRESS | ||
| Line 25: | Line 22: | ||
- include a index across select/omit fields | - include a index across select/omit fields | ||
6. Compile all logical files (including the "old physical") | 6. Compile all logical files (including the "old physical") | ||
| + | |||
| + | [[Category:SQL|DDS to SQL DDL]] | ||
Revision as of 22:10, 7 December 2007
WORK IN PROGRESS - please help by editing this document - include code/specific commands where needed
SQL described tables work better (faster and more efficiently) than DDS described files.
How to convert from DDS to SQL without breaking existing programs...
Big picture...create a new SQL table to hold the data, build indexes across this new table, rebuild the physical file DDS as a logical file, change the logicals to point at new physical.
1. Retrieve the SQL for your physical table using API or iNavigator.
- change the name of the table to match your company standards - for example, physical file MSPMP100, new SQL name MSPMP100SQ - use old format name for new table
2. Retrieve list of key fields used across the file 3. Build indexes using longest number of key fields to shortest 4. Rebuild the physical file DDS to be a logical file 5. Change the logical files to point to new physical
- if logical uses select/omit change to use dynslt - include a index across select/omit fields
6. Compile all logical files (including the "old physical")
