JA Technology Solutions
DDS to SQL / SQL to DDS Converter
Convert between IBM i DDS physical file definitions and SQL CREATE TABLE statements in both directions.
DDS to SQL / SQL to DDS Converter
Convert DDS physical file definitions to CREATE TABLE statements in 5 SQL dialects (ANSI, DB2 for i, PostgreSQL, MySQL, SQL Server), or convert SQL CREATE TABLE back to DDS source bidirectionally. Each dialect uses its native type names and syntax conventions. Handles type mappings between DDS types (A, P, S, B, L, T, Z) and SQL types, key fields, NOT NULL constraints, and field descriptions. Drop a DDS or SQL source file, or paste content directly; copy the converted output or download it as a file. Runs entirely in your browser — your schemas never leave your machine.
Learn more ↓
Loading interactive explorer...
DDS vs SQL on IBM i
IBM i supports two ways to define database tables: DDS (Data Description Specifications) physical files and SQL CREATE TABLE statements. DDS has been available since the System/38 and uses a columnar source format with type codes like A (character), P (packed decimal), S (zoned decimal), B (binary), L (date), T (time), and Z (timestamp). SQL DDL is the modern approach and offers features DDS cannot provide — identity columns, check constraints, views, triggers, and more. IBM recommends SQL for new development, but thousands of production files still use DDS definitions.
Why Convert Between DDS and SQL?
Converting DDS to SQL is a common step in IBM i modernization — moving from DDS-defined physical files to SQL-managed tables enables modern database features and makes the schema accessible to SQL-based tools and reporting platforms. The reverse direction (SQL to DDS) is useful when integrating with legacy applications that expect DDS-defined files, or when documenting an existing SQL table in DDS format for teams familiar with that notation. This tool maps DDS types to their SQL equivalents across five dialects (ANSI, DB2 for i, PostgreSQL, MySQL, SQL Server) and preserves key fields, NOT NULL constraints, and field descriptions.
Database Migration Services
Converting individual file definitions is straightforward, but a full database migration involves hundreds of files, cross-references between physical and logical files, embedded SQL in RPG programs, and data validation across the entire schema. I handle complete IBM i database migrations — from initial assessment through schema conversion, data migration, and application testing. Learn about IBM i services, explore migration capabilities, or get in touch to discuss your database migration project.
All tools run entirely in your browser. Your data never leaves your machine. Need help? Ask James.