> ## 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 Databricks

> Learn how to securely connect Julius to your Databricks SQL warehouse to analyze your data directly without uploading files.

<div style={{ display: "flex", justifyContent: "center" }}>
  <iframe width="560" height="315" src="https://www.youtube.com/embed/DAckcJI1WeY?si=ywnFHxZR23Up_jwi&start=2" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen />
</div>

## Getting Started

Julius connects directly to your Databricks SQL warehouse, 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 **Databricks**.
  </Step>
</Steps>

***

## Connection Setup

### Required Fields

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

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

  **Example:** "Prod Databricks Warehouse" or "Marketing Analytics Workspace"
</ParamField>

<ParamField path="SERVER_HOSTNAME" type="string" required>
  The Databricks workspace hostname.

  **Example:** `adb-1234567890123456.7.azuredatabricks.net`
</ParamField>

<ParamField path="HTTP_PATH" type="string" required>
  The HTTP path for your Databricks SQL warehouse or cluster endpoint.

  **Where to find it:** In Databricks, go to your SQL warehouse, click **Connection details**, and copy the **HTTP Path** value.
</ParamField>

<ParamField path="ACCESS_TOKEN" type="string" required>
  A Databricks personal access token (PAT) or equivalent credential with permission to query the warehouse.

  **Security:** Julius encrypts and securely stores this token.
</ParamField>

<ParamField path="CATALOG" type="string" required>
  The Databricks catalog Julius should use by default.

  **Example:** `main` or your organization's primary catalog.
</ParamField>

<ParamField path="SCHEMA" type="string" required>
  The default schema within the catalog that Julius will query.

  **Example:** `analytics`, `public`, or another schema that contains your tables.
</ParamField>

<ParamField path="MFA_TYPE" type="string">
  Optional multi-factor authentication type if your organization requires MFA for Databricks access.

  **Most users:** Can leave this blank unless specifically required by your security policy.
</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">
      * ✓ Host 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 customers from the users table"
  </Card>

  <Card title="Calculate Metrics" icon="calculator">
    "What's the average order value this month?"
  </Card>

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

  <Card title="Analyze Trends" icon="chart-mixed">
    "How has revenue 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 least-privilege credentials" icon="lock">
    Create a dedicated Databricks service principal or user with read-only access to the catalogs and schemas Julius needs. Avoid using admin tokens or workspace-wide admin accounts.
  </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">
    Work with your database administrator to ensure proper security policies 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 host 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>
