To use Looker with Actian Avalanche or Vector, you will need to configure an Ingres driver. These instructions describe that process, assuming use of a startup script that is similar to the examples that are provided on the [looker-open-source GitHub page](https://github.com/looker-open-source/customer-scripts/tree/master/startup_scripts).

You will need to acquire an Ingres driver JAR, include it as part of the startup process, and add an option to tell Looker to access it.

## Encrypting network traffic

It is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options that are described on the [Enabling secure database access](https://docs.cloud.google.com/looker/docs/2622/enabling-secure-db-access.md.txt) documentation page.

## Installing the Ingres JDBC driver

Follow the steps on the [Unpackaged JDBC drivers](https://docs.cloud.google.com/looker/docs/2622/unpackaged-jdbc-drivers) documentation page using the following values:

**driver symbol** : `ingres`

**driver entry**:

    - name: ingres
      dir_name: ingres
      module_path: com.ingres.jdbc.IngresDriver

For the [step to put the driver in your dialect's directory](https://docs.cloud.google.com/looker/docs/2622/unpackaged-jdbc-drivers#driver_directory), the path to this file will look like this: `looker/custom_jdbc_drivers/ingres/iijdbc.jar`.

## Creating the Looker connection to your database

Follow these steps to create the connection from Looker to your database:

1. In the **Admin** section of Looker, select **Connections** , and then click **Add Connection**.
2. Select **Actian Avalanche** or **Vector** from the **Dialect** drop-down menu.

   > [!NOTE]
   > **Note:** If you are on a [Looker (Google Cloud core)](https://docs.cloud.google.com/looker/docs/looker-core-overview.md.txt) instance and you don't see your dialect listed in the **Dialect** drop-down menu, see the [Looker (Google Cloud core) documentation](https://docs.cloud.google.com/looker/docs/looker-core-dialects.md.txt#supported_dialects_for) to verify that the dialect is supported for Looker (Google Cloud core) instances.

3. Fill out the connection details. The majority of the settings are common to most database dialects. See the [Connecting Looker to your database](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt) documentation page for information.

4. To verify that the connection is successful, click the **Test Connection** button in the **Status details** section at the bottom of the **Connections Settings** page.

5. If Looker displays **Can Connect** , press **Connect** to create the connection.

Your database connection is then added to the list on the Looker [**Connections**](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt) **Admin** page.

## Enabling PDT support

It is possible to use [persistent derived tables (PDTs)](https://docs.cloud.google.com/looker/docs/2622/derived-tables.md.txt#persistent_derived_table) on your database using the [**PDT Overrides**](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#configuring_separate_login_credentials_for_pdt_processes) section in the [**Connection Settings** page](https://docs.cloud.google.com/looker/docs/2622/admin-panel-database-connections.md.txt#adding_connections).

To enable PDTs:

1. Create a PDT user in your database for use with the scratch schema, for example `looker_scratch`.

2. Create a group in your database such as `looker_pdt_group`.

3. Add both the regular Looker user and the Looker PDT user to the new group.

4. GRANT SELECT on all tables in the regular Looker user's schema to the PDT user.

5. In the Looker **Connection Settings** page, in the **PDT Overrides** section, enter the PDT user information.

6. The PDT user then runs a GRANT SELECT to the `looker_pdt_group` for every table it creates.

## Supported JDBC parameters

The following sections provide a list of JDBC parameters that are allowed for each dialect:

- [Actian Avalanche](https://docs.cloud.google.com/looker/docs/2622/db-config-actian-avalanche-and-vector.md.txt#avalanche)
- [Vector](https://docs.cloud.google.com/looker/docs/2622/db-config-actian-avalanche-and-vector.md.txt#vector)

### Actian Avalanche JDBC parameters

For Actian Avalanche, Looker supports the following JDBC parameter in the [**Additional JDBC parameters**](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#additional_jdbc_parameters) field for the connection. See the documentation for your database for information on these parameters.

- `autocommit_mode`
- `encryption`
- `password`
- `send_ingres_dates`
- `serverName`: For public Looker instances, the value for the `serverName` parameter must be the public IP address of the instance.
- `user`

### Vector JDBC parameters

For Vector, Looker supports the following JDBC parameters in the [**Additional JDBC parameters**](https://docs.cloud.google.com/looker/docs/2622/connecting-to-your-db.md.txt#additional_jdbc_parameters) field for the connection. See the documentation for your database for information on these parameters.

- `autocommit_mode`
- `encryption`
- `password`
- `send_ingres_dates`
- `serverName`: For public Looker instances, the value for the `serverName` parameter must be the public IP address of the instance.
- `user`

## Feature support

For Looker to support some features, your database dialect must also support them.

### Actian Avalanche

Actian Avalanche supports the following features as of Looker 26.22:

| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | No |
| Symmetric aggregates | Yes |
| Derived tables | Yes |
| Persistent SQL derived tables | Yes |
| Persistent native derived tables | Yes |
| Stable views | Yes |
| Query killing | Yes |
| SQL-based pivots | Yes |
| Time zones | No |
| SSL | No |
| Subtotals | No |
| JDBC additional params | Yes |
| Case-sensitive | Yes |
| Location type | Yes |
| List type | Yes |
| Percentile | No |
| Distinct percentile | No |
| SQL Runner Show Processes | No |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | Yes |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | No |
| OAuth 2.0 credentials | No |
| Context comments | Yes |
| Connection pooling | No |
| HLL sketches | No |
| Aggregate awareness | Yes |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | Yes |
| Materialized views | No |
| Period-over-period measures | No |
| Approximate count distinct | No |
| In-database analytic models | No |
| Custom calendars | Yes |

### Vector

Vector supports the following features as of Looker 26.22:

| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | No |
| Symmetric aggregates | Yes |
| Derived tables | Yes |
| Persistent SQL derived tables | Yes |
| Persistent native derived tables | Yes |
| Stable views | Yes |
| Query killing | Yes |
| SQL-based pivots | Yes |
| Time zones | No |
| SSL | No |
| Subtotals | No |
| JDBC additional params | Yes |
| Case-sensitive | Yes |
| Location type | Yes |
| List type | Yes |
| Percentile | No |
| Distinct percentile | No |
| SQL Runner Show Processes | No |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | Yes |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | No |
| OAuth 2.0 credentials | No |
| Context comments | Yes |
| Connection pooling | No |
| HLL sketches | No |
| Aggregate awareness | Yes |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | Yes |
| Materialized views | No |
| Period-over-period measures | No |
| Approximate count distinct | No |
| In-database analytic models | No |
| Custom calendars | Yes |