Import From JDBC Connection

Import From JDBC Connection is available under the Import tab and is only available for Datatypes and Data Asset Collections.

Functionally, import from JDBC has the same purpose as from a import of a DDL File, except that the DDL source is a live connection to a database server, rather than a DDL file.

JDBC version 4 database drivers can be added by your systems IT. ex: tomcat/webapps/edg/WEB-INF/lib. Please have your DBA review the terms of the driver for compliance

The parameters for the import are:

Model for Datatype Definitions: If not available, create a new EDG Datatype collection which will automatically be populated with some standard data

JDBC URL: The connection address-string, which may depend on the database type (e.g., jdbc:mysql://localhost:3306/mydb123)

User Name and Password: A database login with access to the desired tables.

Note

If the password is already in EDG’s secure storage, it may be omitted.

Database name: the desired database/schema that identifies the scope of this DDL import operation, . If not provided, the import will use the default scope of the user or connection.

Include data statistics: If checked, this will compute statistics summarizing the data contained in each imported entity (table, view) and column. Edit or view the data asset collection and select each asset item to see the details of its resulting statistics.

Include data samples: If checked, this will collect sample rows from each entity (table, view). Edit or view the data asset collection and select each entity table or view to see the sample data.

Maximum number of data samples per table: When including data samples, the upper limit of rows to collect from each table for the sample data.

Record each new triple in change history: If checked, each imported triple is recorded in change history, which is not recommended for large imports.

Note

This option is not visible if Record Triple Count option under the Manage tab is activated.

Schedule Import: lets the user schedule imports to run on a recurring schedule.