Securely configure Looker to query data stored in Microsoft SQL Server.
Looker can only visualize data held in a database it can reach. Adding SQL Server lets analysts create dashboards without copying data.
Confirm you have (a) a SQL Server hostname or IP, (b) a SQL login with read rights, (c) the port open (default 1433) to the Looker IP(s), and (d) SSL certificates if required.
Navigate to Admin → Connections → New Connection. Choose “Microsoft SQL Server.” Supply the values below, save, and test.
Name: lowercase, no spaces (ex: sqlserver_ecommerce
)
Host: db.company.com
Port: 1433
Database: ecommerce
Username/Password: service account
SSL: enable to encrypt traffic.
PDT Support: allow Looker to create Persistent Derived Tables.
Open SQL Runner, pick the new connection, and run a simple query such as:
SELECT TOP 5 id, name, email FROM Customers ORDER BY created_at DESC;
Grant the Looker user read-only access to base schemas and db_ddladmin or a dedicated schema for PDTs only when needed. Monitor query cost with SQL Server DMVs.
“Could not connect” → verify firewall and SSL settings.
“Login failed” → confirm SQL authentication (not Windows) and password.
“Database unavailable” → check the chosen default database exists.
Create a user-mapped role and grant SELECT
only on needed tables, e.g. GRANT SELECT ON dbo.Orders TO looker_ro;
No. Looker’s hosted platform already bundles the Microsoft JDBC driver. For customer-hosted Looker (Looker on prem), install mssql-jdbc-<ver>.jar
in the drivers folder.
Only via Persistent Derived Tables (PDTs). Enable PDT Support and grant CREATE TABLE
on the target schema.
Yes. Use the same connector. Whitelist Looker IP ranges in the Azure firewall and ensure encrypt=true
.