We can help you with your Document Management needs!!!

(949) 709-5838 / (800) 858-5544

Move from DDS to SQL

Why SQL? – Move from DDS to SQL

The old traditional method for database structure and management is DDS (Data Description Specifications) on the IBM i (going back decades to the iSeries and AS400 days). This is already known to be an outdated method. Modernization is a must to compete in today’s IT world!

The IBM preferred method is to migrate the DDS database to the DDL (SQL) SQL database structure:

IBM White Paper DDS and SQL – The Winning Combination for DB2 for i: Business and technical benefits of a modern DB2 for i database

Data-Centric Programming: Let the database do more for you:

IBM has been making significant strides on SQL and DB2 technology since 1999. And nothing on DDS. Drive work into the database instead of the application, all decision making and management happens at the data base level, reducing the need to keep track of all changes and updates by modifying and updating programs.

Improve Consistency and Efficiency:

From our experience overall performance gain is over 20%

Open up new ways to access data:

PHP, JDBC, ODBC, .NET, CL You will basically open up the IBM i platform to all access methods that every other platform is using. The ROI is obvious. Extend the life of the IBM i without having to rip and replace the system or application.

Attract talented SQL programmers and update skill of existing staff:

Staying current with today’s IT trends are mandatory. Once modernized to SQL, your company will be able to compete with modern trends and applications, while attracting talented SQL staff.

SQL is the strategic database interface for nearly all platforms, including IBM i.

Why AO? (instead of the other solutions)

Remain on our reliable IBM i:

Without using the AO solution the company will have to ‘modernize’ another way, by ‘retiring’ the IBM i (iSeries) to a Windows based new platform. Experience has proven this to be costly, resource (people) consuming, re-educating IT personnel and user departments.

Let’s do the conversion by hand:

Take a good like at how many libraries, physical files, logicals, dependent files, constraints and triggers that need to be considered for SQL conversion. If converted by hand, one by one, this will tie up IT staff time and become quite costly. Let us provide our ROI calculator to help you estimate.


AO is the only conversion tool to provide management of multiple instances of the same schema. By creating a ‘Master’ schema you can control the changes and additions to the ‘Shadow’ schemas.

Adding, removing, changing keys, of a table in the master schema is populated automatically to the shadow schema.

This allows for ‘node synchronization’ providing reports and information for regulatory requirements and simplifying database management.

Tags: dds move