Getting Started
Julius connects directly to your Databricks SQL warehouse, allowing you to analyze your data using natural language; no SQL knowledge required.Connection Setup
Required Fields
All fields marked with an asterisk (*) are required.
MFA_TYPE is optional.A friendly name to identify this Databricks connection in Julius.Example: “Prod Databricks Warehouse” or “Marketing Analytics Workspace”
The Databricks workspace hostname.Example:
adb-1234567890123456.7.azuredatabricks.netThe 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.
A Databricks personal access token (PAT) or equivalent credential with permission to query the warehouse.Security: Julius encrypts and securely stores this token.
The Databricks catalog Julius should use by default.Example:
main or your organization’s primary catalog.The default schema within the catalog that Julius will query.Example:
analytics, public, or another schema that contains your tables.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.
Network Configuration
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
- ✓ Host and port are correct
- ✓ 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 customers from the users table”
Calculate Metrics
“What’s the average order value this month?”
Create Visualizations
“Create a chart of sales by region”
Analyze Trends
“How has revenue 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 least-privilege credentials
🔐 Use least-privilege credentials
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.
🧪 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
Work with your database administrator to ensure proper security policies 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 host or port
- Database doesn’t allow external connections
- 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 team@julius.ai for assistance
