In some environments, direct access to the application database may not be available due to security restrictions, network limitations, or infrastructure constraints. In such cases, analysing the database schema directly from the source system is not possible. However, the data model can still be extracted and analysed using DDL (Data Definition Language) files.
DDL files contain the structural definitions of database objects such as tables, indexes, views, and other schema components. These files can be generated by a Database Administrator (DBA) or exported from the database management system. By importing these DDL scripts into Visual Expert, the tool can reconstruct the database structure and integrate it into the project analysis.
This approach allows teams to analyse the data model, understand database relationships, and include database objects in the overall application documentation — even when a direct connection to the database is unavailable. It ensures that database structures remain part of the application analysis and documentation process within Visual Expert.
If Visual Expert cannot connect directly to the application database, you can still analyse the data model by importing DDL files containing the definitions of the database objects.
Follow the steps below:
Create text files containing the DDL statements that define the structure of the database. These files typically include statements such as:
CREATE TABLECREATE INDEXCREATE VIEWIn some cases, these scripts may already exist as part of the project resources. If not, a Database Administrator (DBA) can generate them directly from the database.
Once the scripts are generated, place all the DDL files in a folder that is accessible by Visual Expert. This folder will be used as the source from which Visual Expert reads and analyses the database object definitions.
You must add the folder containing the DDL files as a new source of code in your Visual Expert project.
To do this:
For quick reference on adding a source, see the articles below:
When adding the source, choose the source type according to the database used by the application:
This allows Visual Expert to correctly interpret the database definitions contained in the DDL files.
You must declare a dependency between the application source code and the database source so that Visual Expert can link the database objects with the application.
To configure this:
For more guidelines on adding source code and dependencies, refer to: Define Cross-Application Dependencies.
After completing these steps, run the project analysis so Visual Expert can parse the DDL files and integrate the database objects into the project documentation and analysis.