Vertica

Vertica is a columnar analytics database built for large-scale queries. Point TableR at your Vertica host by filling the connection form.

Overview

TableR connects to Vertica over its native protocol. It works with a self-hosted cluster or a managed Vertica service; the columnar storage is designed for analytical (OLAP) workloads over large datasets.

• Self-hosted — connect to your Vertica host on port 5433.
• Remote / managed — use the provider endpoint and enable SSL/TLS.
• Columnar analytics — optimized for large scans and aggregations rather than single-row lookups.

Before you start

• A reachable Vertica host (host and port).
• A database user name — this is required.
• The user's password, if the database requires one.
• Optionally, the specific database to open on connect.
• For remote hosts: network access to the port and, usually, SSL/TLS enabled.

Connection fields

These defaults match TableR's Vertica connection form. Secrets are written to the operating system keyring, never to plain configuration files.

Connect with the form

1. 1
   Choose Vertica

   Open the launcher and pick the Vertica card.

2. 2
   Enter host and port

   Use 127.0.0.1 and 5433 for a local host, or your provider's endpoint for a remote one.

3. 3
   Add credentials

   Type the username, and the password if required. The password is saved to the OS keyring.

4. 4
   Pick a database (optional)

   Set a database to open it directly, or leave it blank to use the user's default.

5. 5
   Enable SSL/TLS for remote

   Turn on SSL/TLS when connecting to a remote or managed host.

6. 6
   Save and connect

   Save the profile so it reappears in the launcher, then connect.

SSL/TLS

Local hosts on 127.0.0.1 usually need no encryption. For anything over a network, enable SSL/TLS so credentials and results are protected in transit.

• Off — no encryption (local or trusted networks only).
• On — encrypt the connection to the Vertica host.
• Enable it for any remote or managed host.

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT version();
SELECT current_database(), current_user;

If both statements return rows, the connection and credentials are working.

Troubleshooting

Next steps