Vertica
Connectivity Summary
An out of the box connector is available for Vertica databases. It provides support for crawling database objects, profiling of sample data and lineage building.
The connectivity to Vertica is via JDBC driver, which is included in the platform.
The drivers used by the connector are given below:
Driver / API: Vertica JDBC Driver
Version: 7.0
Details: https://ovaledge.s3-us-west-1.amazonaws.com/OvalEdge+Clients/Jars/vertica-jdbc-7.0.1-0.jar
Connector Capabilities
The connector capabilities are shown below:
Crawling
Supported objects for Crawling are:
Tables
Table Columns
Views
Please see this article Crawling Data for more details on crawling.
Profiling
Please see Profiling Data for more details on profiling.
Feature
Support
Remarks
Table Profiling
Row count, Columns count, View sample data
View Profiling
Row count, Columns count, View sample data
View is treated as a table for profiling purposes
Column Profiling
Min, Max, Null count, distinct, top 50 values
Full Profiling
Supported
Sample Profiling
Supported
Querying
Operation
Details
Select
Supported
Insert
does not support subqueries as the target of an INSERT statement
Update
Not supported, by default.
Delete
Does not support no self joins.
Joins within database
Supported
Joins outside database
Not supported
Aggregations
Supported
Group By
Supported
Order By
Supported
By default the service account provided for the connector will be used for any query operations. If the service account has write privileges, then Insert / Update / Delete queries can be executed.
Pre-requisites
To use the connector, the following need to be available:
Connection details as specified in the following section should be available.
A Service account, for crawling and profiling. The minimum privileges required are:
Connection validate
Crawl Schemas
Crawl Tables
Profile Schemas, Tables
Query logs
Get Views, Procedures, Function code
JDBC driver is provided by default. In case it needs to be changed, add Vertica client drivers into the OvalEdge Jar path to communicate to Vertica database.
Check the Configuration section for further details on how to add the drivers to the jar path.
Connection Details
The following connection settings should be added for connecting to a Vertica database:
Database Type: Vertica
Connection Name: Select a Connection name for the Vertica database. The name that you specify is a reference name to easily identify your Vertica database connection in OvalEdge.
Hostname / IP Address: Database instance URL Example: 54.210.69.0(varies)
Port number: 5433
Sid / Database: Name of the database to connect.
Username: User account login credential.
Password: Password
Driver Name: JDBC driver name for Vertica. It will be auto-populated. Example: com.vertica.jdbc.Driver
Connection String: Vertica connection string. Set the Connection string toggle button to automatic, to get the details automatically from the credentials provided. Alternatively, you can manually enter the string. Format: jdbc:vertica://{server}:5433/{sid}
Once connectivity is established, additional configurations for Crawling and Profiling can be specified.
Property
Details
Crawler configurations
Tables, Views Columns
By default it is selected true
Relationships
Need to select for crawl relationships
Crawler rules
Default include tables regex has regex = (.*) , which can crawl all the tables
Profiler Settings
Tables and columns
By default it is selected true
Views and columns
By default it is selected true
Profile Rules
Default include tables regex has regex = (.*) , which can profile all the tables
FAQs
How much does the driver cost? The JDBC Driver for Vertica is available at no additional charge.
Can I use the driver to access Vertica from a Linux computer? Yes, you can use the driver to access Vertica from Linux and Unix platforms.
Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA
Was this helpful?