Skip to main content
Version: v1.13 print this page

JDBC Connections

These connections are used to migrate data from a JDBC source(s) to Amorphic Data Cloud. Using these connections, data can be written directly into an Amorphic Dataset.

Following are the fields required to establish a JDBC connection,

  • Data load type: There are three types of JDBC Connections available depending on the data load type.

    • Bulk data load
    • Bulk data load v2
    • Normal data load
  • Connection Accessibility: The accessibility type depend on where the data source resides. Following are two options available

    • Publicly Accessible Connection
    • Private Connection
  • JDBC connection url: The data source's JDBC connection url from which the data is to be migrated. Few example formats are listed below:

    - General format: jdbc:protocol://host:port/dbname
    - jdbc:protocol://host:port;dbname=<name>
    - jdbc:oracle:thin:@//HostName:Port/ServiceName(or)SID
    - jdbc:sqlserver://<servername>\<instancename>:port;databaseName=<name>
  • Username: Username for the data source

  • Password: Password for the data source

  • SSL: This field only applies to the Normal data load connections and is used when additional level of security needs to be enforced.

What Data load types apply to your use case?

As mentioned above, Amorphic recognizes JDBC connections as either Bulk or Normal data loads.

Bulk data load connections

Bulk load connections are recommended to the user(s) who wish to migrate quite a few number of tables or significant amount of data. The user entered JDBC url format varies on the database in use. Currently the following data source(s) are supported with this connection type,

  • Oracle
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
  • IBM Db2 (LUW)
  • Aurora MySQL

Creating a Bulk data load JDBC connection (V1 or v2) can be done as shown in the image below,

JDBC Bulk Load Connection Below is the difference between Bulk Data Load & Bulk Data Load v2.

  • Bulk Data Load - As part of the task Amorphic creates datasets before ingesting the data into them. In this process user has to provide metadata which will be used for the creation. This connection type is used when datasets needs to be created in Amorphic with the same schema as that of source. For more details, Please check the documentation on How to set up bulk data load in Amorphic
  • Bulk Data Load v2 - As part of the task user have to select which pre-existing dataset of Amorphic needs to be used to ingest the data into. Also, this connection type is used when multiple tables from source needs to be ingested into a single dataset of Amorphic (Possible only for S3 target type of datasets). For more details, Please check the documentation on How to set up bulk data load (Version 2) in Amorphic

Normal data load connections

Normal load connections are recommended to the user(s) who wish to migrate one table or data that is smaller in size. The user entered JDBC url format varies on the database in use. This connection supports all the data sources that AWS Glue supports (here) as follows,

  • Amazon Redshift
  • Amazon Relational Database Service
    • Amazon Aurora
    • Microsoft SQL Server
    • MySQL
    • Oracle
    • PostgreSQL
  • Publicly accessible databases
    • Amazon Aurora
    • MariaDB
    • Microsoft SQL Server
    • MySQL
    • Oracle
    • PostgreSQL
    • IBM Db2 (LUW)

Creating a Normal data load JDBC connection can be done as shown in the image below,

JDBC Normal Load Connection

Version Enables the user to select what version of ingestion scripts to use (Amorphic specific). For any new feature/Glue version that gets added to the underlying ingestion script, new version will be added to the Amorphic.

Upgrade

User can upgrade a connection (if available) which will be shown in the options. Upgrade option is visible only if there is any new version available else it is not shown.

Connection upgrade upgrades the underlying Glue version and the data ingestion script with new features.

Below image shows how to upgrade a connection Upgrade jdbc Connection

Downgrade

User can downgrade a connection to previous version if he thinks the upgrade is not serving the purpose. A connection can only be downgraded if it has been upgraded. For a connection that has been created we cant downgrade it. Downgrade option in JDBC connections is available in Normal data load The option to downgrade is available on the top right corner if the connection is downgrade compatible.

Note

Upgrade option is only applicable for jdbc normal load connection