Skip to main content

​
Getting Started

Julius connects directly to your SQL Server 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 SQL Server.

Choose Your Connection Mode

Select how you’ll connect to your database:
  • Direct: Connect directly to your SQL Server database
  • SSH: Connect through an SSH tunnel for enhanced security

​
Connection Setup

  • Direct Connection
  • SSH Connection

​
Required Fields

All fields marked with an asterisk (*) are required.
​
Connection Name
string
required
A friendly name to identify this SQL Server connection in Julius.Example: “Production SQL Server” or “Reporting Database”
​
Server
string
required
The SQL Server hostname or IP address, optionally with an instance name.Examples: sql-prod.mycompany.com, 10.0.0.5, or sql-prod\\analytics
​
User
string
required
Your SQL Server login/user with read permissions on the target database.
Create a dedicated read-only user for Julius.
​
Password
string
required
Password for your SQL Server login.Security: Encrypted in transit and at rest.
​
Database
string
required
The specific SQL Server database name to analyze.Example: Sales, Analytics, Reporting
​
Port
number
required
The network port for SQL Server connections.Default: 1433Note: Only change if your SQL Server is listening on a custom port.

​
Network Configuration

Whitelist Julius IP Address

If your database has firewall restrictions, you’ll need to allow connections from Julius.

IP Whitelisting Guide

Step-by-step instructions for AWS RDS, Google Cloud SQL, Azure, and other platforms

Get Julius IP Address

Find your current Julius IP in Data Connectors settings

Test Your Connection

  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!
  • ✓ Host 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 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?”
No SQL required! Julius automatically writes and executes queries based on your natural language requests.

​
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

Create a dedicated SQL Server login/user with read-only permissions to prevent accidental data modification.
    -- Create a login at the server level
    CREATE LOGIN julius_readonly WITH PASSWORD = 'StrongPasswordHere!';

    -- Map the login to a user in your database
    USE YourDatabaseName;
    CREATE USER julius_readonly FOR LOGIN julius_readonly;

    -- Grant read-only access
    ALTER ROLE db_datareader ADD MEMBER julius_readonly;
Verify your connection works correctly using a development or staging database before connecting to production.
Work with your database administrator to ensure proper security policies and performance guidelines are followed.
Keep an eye on database load when running complex queries through Julius, especially on production systems.

​
Troubleshooting

Possible causes:
  • Incorrect host or port
  • Database doesn’t allow external connections
  • Julius IP not whitelisted
  • Database is offline or unreachable
Solution: Verify all connection details and check firewall settings
Possible causes:
  • Wrong username or password
  • User lacks database permissions
  • Database name misspelled
Solution: Double-check credentials and verify user permissions
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

​
Need Help?