The Connections page lists all of the database connections that you have configured for Looker use. To access the Connections page, open the Admin menu and, under Database, choose Connections.
This page shows basic information about database connections you’ve defined and, if the ability to create a new database has been enabled for your instance, any Looker-managed connections you’ve created. You can also test the status of those connections:
|Name||The name of the connection, chosen by you, that is used in the
|Host:Port||The host path where your database is located, and the port that Looker will use to connect to that host.|
|Username||The username that Looker will use to connect to the database.|
|Database||The name of the database that Looker will query when using this connection.|
|SSL||Whether or not you are using SSL encryption to protect the data traveling between Looker and your database (please note there are other secure options that are not SSL).|
|Type||The SQL dialect of the database connection.|
|Actions||Actions you can take for a connection: test a connection, edit a connection, view other information about a connection, jump to a list of links to the connection’s Explores, or delete a connection. If the ability to create a new database has been enabled for your instance, you can also add data from an additional data source to any Looker-managed connections.|
Looker lets you test your existing connections to make sure they are functioning properly. You can also test connections as you add them, as described on the Connecting Looker to Your Database documentation page.
Each connection test includes a list of status checks to tell you whether or not Looker can successfully use the database connection. For example:
Potential issues are shown in yellow, while errors are shown in red. If a connection “passes” it will appear in green.
Database connections that use OAuth, such as Snowflake and Google BigQuery, require a user login. If you are not logged in to your OAuth user account when you test one of these connections, Looker will show a warning with a Log In link. Click the link to enter your OAuth credentials or allow Looker access to your OAuth account information.
You can check the status of:
- A single connection by clicking Test to the far right of that connection
- All connections by clicking the Test All Connections button at the top of the page
Two checks are common cause for confusion:
- Can find temp schema
- Can use persistent derived tables
These checks do not need to pass in order for Looker to function. However, you will need them to pass in order to use persistent derived tables, which are a very valuable modeling feature.
To add a new database connection, follow the steps described on the Connecting Looker to Your Database documentation page.
To edit an existing connection, click the Edit button to the far right of each connection. You’ll be brought to same page that you use to create a connection (described on the Connecting Looker to Your Database documentation page), but with the relevant information already filled out. Make any changes you need to, then click Update Connection.
Other Connection Actions
The following options are available from the gear drop-down menu to the far right of each connection.
Actions Available for All Connections
All connections offer these options:
This option brings you to Looker’s SQL Runner, with the proper connection and schema already selected.
This option brings you to a list of basic, automatically-generated Explore options for your connection. These are not based on your customized data models, but they enable some quick reporting on the raw data in your connection’s tables. This is typically only useful for getting an idea of table contents before modeling, rather than for the purposes of actual data analysis.
To delete an existing connection, click the gear drop-down menu to the far right of a connection and select Delete. You’ll be given the opportunity to confirm the deletion but, once you do so, it cannot be undone. Accidentally deleting a connection will disable any queries that use it. However, as long you re-create a new connection with the same name, functionality will be restored.
Actions Available for Some Connections
Depending on the connection dialect, the gear drop-down menu to the right of the connection may offer the following additional options:
This option brings you to a Looker Explore page that lets you create Looker reports based on the metadata of your connection. Although this option begins with the schema name, table name, and column count selected, you can manipulate it just like any other Looker report.
This option brings you to a Looker Explore page that lets you create Looker reports based on the metadata of your connection. Although this option begins with the schema name, catalog name, table count, and column count selected, you can manipulate it just like any other Looker report.
This option brings you to a Looker Explore page that lets you create Looker reports based on the processes running on this connection, the state they are in, how long they have been running, and other info. This can be useful in helping determine the cause if Looker is running slow, or if a query is not running at all.
Show PDT Event Log
This option brings you to a Looker Explore page that lets you create Looker reports based on the derived table activity for this connection. The available fields are described in more detail on our PDTs documentation page.