DbVisualiser

DbVisualizer is a versatile SQL editor and universal database tool, available as an open-source application for local installation on your workstation. By leveraging the JDBC driver, DbVisualizer enables seamless access to e6data clusters, empowering users with efficient database management capabilities.

Requirements

• Users of the e6data cluster must use DbVisualiser 23.2.4 or newer.

• Install the latest e6data jdbc driver

Connection

Get the necessary connection information for your cluster:

• JDBC URL

• Username

• Password (Personal Access Token)

Connection string for Direct Connectivity Endpoint

Syntax of the JDBC URL required to establish a DB Visualiser connection with the e6data cluster when connecting using the Direct type of connectivity in endpoints:

jdbc:e6data://<host>:<port>/database=<database_name>&catalog=<catalog_name>

Connection string for TLS Connectivity Endpoint

Please refer to the syntax of the JDBC URL required to establish a DB Visualiser connection with the e6data cluster when connecting via TLS type of connectivity in endpoints:

jdbc:e6data://<host_name>:<port./database=<database_name>&catalog=<catalog_name>&secure=true&cluster-uuid=<cluster_uuid>

1. Click on "Create Database" to establish a new connection.

2. Search and select "Custom" from the connection list.

1. Give the appropriate name for the driver.

2. In the settings format, select the database URL.

3. Give the connection string in the database URL.

1. Click "Connect" to add the JDBC jar through the driver manager.

2. Now, open the Driver Manager, provide the name, and JDBC connection string, and add the driver here.

1. Go to the database connection, add the database URL, database user ID, and password, and click on "Connect."

TLS/HTTP

e6data utilizes globally trusted certificates, ensuring that the host and port provided by the connection dialogue are adequate. Any e6data cluster necessitating authentication must also employ TLS/HTTPS. If adhering to globally trusted certificate best practices, utilize the cluster’s HTTPS URL in the connection string as detailed in the aforementioned steps. (Only required for TLS connectivity type of endpoints.)