All tools

DDS to SQL

Calculations happen on the device in use. Entered data is not transmitted to the server.

DDS to SQL

Paste the DDS of a physical file and get the matching CREATE TABLE.

A R CLIENTECREATE TABLE

What it covers and what it does not

Field definitions are read — name, length, type, decimals — along with the record format and key fields. Type mapping is: A to CHAR, P to DECIMAL, S to NUMERIC, L to DATE, T to TIME, Z to TIMESTAMP, B to SMALLINT, INTEGER or BIGINT depending on length. A field with no explicit type is zoned when it has decimals and character when it does not, as DDS requires. Comments come out as --, and fields that cannot be translated come out commented in full, so the CREATE TABLE still runs and the column to fix by hand stays in sight. Two options change the result: NOT NULL on every field, and long names taken from the description — COLHDG first, then TEXT — with the DDS name kept as FOR COLUMN, the system name RPG programs go on reading the file with. Validation keywords, default values and fields defined by reference are left out, and flagged rather than guessed: the result is a starting point to read through, not something to run blind.

Is a tool you would often use missing? Let us know, gladly.