Getting Started
Julius connects directly to your Vertica database, allowing you to analyze your data using natural language; no SQL knowledge required.Create New Data Connector
Navigate to the Data Connectors page and click “Create new Data Connector”, then select Vertica.
Connection Setup
- Direct Connection
- SSH Connection
Required Fields
All fields marked with an asterisk (*) are required.
A friendly name to identify this Vertica connection in Julius.Example: “Production Vertica” or “Analytics Warehouse”
The Vertica server hostname or IP address.Examples:
vertica-prod.mycompany.com or 10.0.0.5Your Vertica user with read permissions on the target database.
Password for your Vertica user.Security: Encrypted in transit and at rest.
The specific Vertica database name to analyze.Example:
analytics, warehouse, reportingThe network port for Vertica connections.Default:
5433 (Vertica default)Note: Only change if your Vertica instance is listening on a custom port.Network Configuration
Whitelist Julius IP Address
If your Vertica database has firewall restrictions, you’ll need to allow connections from Julius.
IP Whitelisting Guide
Step-by-step instructions for common cloud and on-prem environments
Get Julius IP Address
Find your current Julius IP in Data Connectors settings
Test Your Connection
- Click “Add Connection” to test your configuration
- Julius validates your credentials and network access
- If successful, your connector is ready to use!
Connection failed? Here's what to check
Connection failed? Here's what to check
- ✓ Server and port are correct
- ✓ Julius IP is whitelisted in your firewall
- ✓ Database allows external connections
- ✓ Username and password are accurate
- ✓ User has permissions for the specified database
Start Analyzing Your Data
Once connected, simply ask Julius about your data in plain English:Query Data
“Show me all rows from the events table for the last 30 days”
Calculate Metrics
“What’s the average session duration by country?”
Create Visualizations
“Create a chart of events by day”
Analyze Trends
“How has user activity changed over the past 6 months?”
Security & Compliance
SOC 2 Type 2
Certified to meet strict security standards
End-to-End Encryption
All credentials and data encrypted in transit and at rest
Zero Data Storage
Julius only queries what you request—never stores your data
Security & Trust Center
Learn more about how Julius protects your data and maintains compliance
Best Practices
🔐 Use read-only credentials
🔐 Use read-only credentials
Work with your Vertica administrator to create a dedicated read-only user or role for Julius to minimize risk.
🧪 Test with non-production data first
🧪 Test with non-production data first
Verify your connection works correctly using a development or staging database before connecting to production.
👥 Coordinate with your DBA
👥 Coordinate with your DBA
Ensure proper security policies, resource usage limits, and performance guidelines are followed.
📊 Monitor database performance
📊 Monitor database performance
Keep an eye on database load when running complex queries through Julius, especially on production systems.
Troubleshooting
Connection timeout
Connection timeout
Possible causes:
- Incorrect server or port
- Database doesn’t allow external connections
- Julius IP not whitelisted
- Database is offline or unreachable
Authentication failed
Authentication failed
Possible causes:
- Wrong username or password
- User lacks database permissions
- Database name misspelled
Can't find tables
Can't find tables
Possible causes:
- User lacks read permissions on tables
- Connected to wrong database
- Tables don’t exist in specified schema
Need Help?
Contact Support
Questions? Reach out to [email protected] for assistance
