Delivering an equivalent relational database on anyone of the more popularly used contemporary relational databases
- Highly flexible and adaptive process capable of adjusting to customer requirements
- Highly automated solution.
- No runtime dependency or dependencies on “black-box” technology
- No license and maintenance fees are charged
- Provides for separation of business logic from data access logic
- Automatically handles occurring data items, Group level, Redefined data
- Targets DB2, SQL Server and Oracle on mainframe or distributed platforms
The database conversion process produces a new DDL information which is critical for the conversion of any applications that access data from the ADABAS databases which are being migrated. The rules that will determine how the database access statements are to be modified to access the same data from the new relational database, are present in the new DLL and in the rules file which is produced as part of the DDL generation process.
The conversion process begins with analysing the code and ADABAS definitions in terms of compatibility of the requirements of the target environment i.e. the analyser will seek to identify for example the use of reserved words as variables, or the use of variable names which are either too long or make use of special characters not supported by the target environment. Corrective action may then be manually undertaken prior to the conversion process being initiated.
Once the analysis yields acceptable results the process moves on to the DDL Generation Phase. In this phase the ADABAS DDMs are transformed to equivalent SQL DDL based on the DDM structures and based on the rules predetermined for dealing with any ADABAS specific constructs not supported in the target environment. This process also produces as output the data migration programs that will be used to migrate the ADABAS data from the source ADABAS environment to the new relational database.