Conversion of embedded SQL and application code
The next step is to address any custom scripts with embedded SQL statements (for example, ETL scripts, reports, and so on) and the application code so that they work with the new target database after you convert the database schema. This includes rewriting portions of application code written in Java, C#, C++, Perl, Python, and so on, which relate to JDBC/ODBC driver usage, establishing connections, data retrieval, and iteration. AWS SCT will scan a folder containing application code, extract embedded SQL statements, convert as many as possible automatically, and flag the remaining statements for manual conversion actions. Some applications are more reliant on database objects, such as stored procedures, while other applications use more embedded SQL for database queries.
The workflow for application code conversion is similar to the workflow for database migration:
- An assessment report will estimate the effort to convert the application code to the target platform
- Do code analysis to extract the embedded SQL statements
- AWS SCT will automatically convert as much code as possible
- The remaining conversion has to be done manually
- Save code changes
AWS SCT uses a two-step process to convert application code:
- Extract SQL statements from the surrounding application code
- Convert SQL statements
An Application Conversion Project is a subset of a Database Migration Project. A Database Migration Project is a superset and includes one or more application conversion subprojects where you have a frontend GUI application conversion, an ETL application conversion, and a reporting application conversion. All three applications will be attached to the parent Database Migration Project and converted in the AWS SCT.