> ## Documentation Index
> Fetch the complete documentation index at: https://julius.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup Vertica

> Learn how to securely connect Julius to your Vertica database to analyze your data directly without uploading files.

## Getting Started

Julius connects directly to your Vertica database, allowing you to analyze your data using natural language; no SQL knowledge required.

<Steps>
  <Step title="Create New Data Connector" icon="plus">
    Navigate to the **Data Connectors** page and click **"Create new Data Connector"**, then select **Vertica**.
  </Step>
</Steps>

***

## Connection Setup

### Required Fields

<Note>
  All fields marked with an asterisk (\*) are required.
</Note>

<ParamField path="Connection Name" type="string" required>
  A friendly name to identify this Vertica connection in Julius.

  **Example:** "Production Vertica" or "Analytics Warehouse"
</ParamField>

<ParamField path="Server" type="string" required>
  The Vertica server hostname or IP address.

  **Examples:** `vertica-prod.mycompany.com` or `10.0.0.5`
</ParamField>

<ParamField path="User" type="string" required>
  Your Vertica user with read permissions on the target database.

  <Tip>Create a dedicated read-only user for Julius.</Tip>
</ParamField>

<ParamField path="Password" type="string" required>
  Password for your Vertica user.

  **Security:** Encrypted in transit and at rest.
</ParamField>

<ParamField path="Database" type="string" required>
  The specific Vertica database name to analyze.

  **Example:** `analytics`, `warehouse`, `reporting`
</ParamField>

<ParamField path="Port" type="number" required>
  The network port for Vertica connections.

  **Default:** `5433` (Vertica default)

  **Note:** Only change if your Vertica instance is listening on a custom port.
</ParamField>

***

## Network Configuration

<Steps>
  <Step title="Test Your Connection" icon="plug">
    1. Click **"Add Connection"** to test your configuration
    2. Julius validates your credentials and network access
    3. If successful, your connector is ready to use!

    <Accordion title="Connection failed? Here's what to check">
      * ✓ Server and port are correct
      * ✓ Database allows external connections
      * ✓ Username and password are accurate
      * ✓ User has permissions for the specified database
    </Accordion>
  </Step>
</Steps>

***

## Start Analyzing Your Data

Once connected, simply ask Julius about your data in plain English:

<CardGroup cols={2}>
  <Card title="Query Data" icon="magnifying-glass">
    "Show me all rows from the events table for the last 30 days"
  </Card>

  <Card title="Calculate Metrics" icon="calculator">
    "What's the average session duration by country?"
  </Card>

  <Card title="Create Visualizations" icon="chart-line">
    "Create a chart of events by day"
  </Card>

  <Card title="Analyze Trends" icon="chart-mixed">
    "How has user activity changed over the past 6 months?"
  </Card>
</CardGroup>

<Tip>
  **No SQL required!** Julius automatically writes and executes queries based on your natural language requests.
</Tip>

***

## Security & Compliance

<CardGroup cols={3}>
  <Card title="SOC 2 Type 2" icon="certificate">
    Certified to meet strict security standards
  </Card>

  <Card title="End-to-End Encryption" icon="lock">
    All credentials and data encrypted in transit and at rest
  </Card>

  <Card title="Zero Data Storage" icon="database">
    Julius only queries what you request—never stores your data
  </Card>
</CardGroup>

<Card title="Security & Trust Center" icon="shield-halved" href="https://julius.ai/security">
  Learn more about how Julius protects your data and maintains compliance
</Card>

***

## Best Practices

<AccordionGroup>
  <Accordion title="🔐 Use read-only credentials" icon="lock">
    Work with your Vertica administrator to create a dedicated read-only user or role for Julius to minimize risk.
  </Accordion>

  <Accordion title="🧪 Test with non-production data first" icon="flask">
    Verify your connection works correctly using a development or staging database before connecting to production.
  </Accordion>

  <Accordion title="👥 Coordinate with your DBA" icon="users">
    Ensure proper security policies, resource usage limits, and performance guidelines are followed.
  </Accordion>

  <Accordion title="📊 Monitor database performance" icon="gauge-high">
    Keep an eye on database load when running complex queries through Julius, especially on production systems.
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection timeout" icon="clock">
    **Possible causes:**

    * Incorrect server or port
    * Database doesn't allow external connections
    * Database is offline or unreachable

    **Solution:** Verify all connection details and check firewall settings.
  </Accordion>

  <Accordion title="Authentication failed" icon="key">
    **Possible causes:**

    * Wrong username or password
    * User lacks database permissions
    * Database name misspelled

    **Solution:** Double-check credentials and verify user permissions.
  </Accordion>

  <Accordion title="Can't find tables" icon="table">
    **Possible causes:**

    * User lacks read permissions on tables
    * Connected to wrong database
    * Tables don't exist in specified schema

    **Solution:** Verify user has SELECT permissions and correct database is specified.
  </Accordion>
</AccordionGroup>

***

## Need Help?

<Card title="Contact Support" icon="envelope" href="mailto:team@julius.ai">
  Questions? Reach out to **[team@julius.ai](mailto:team@julius.ai)** for assistance
</Card>