# SQLite

This article outlines the integration with the SQLite connector, enabling metadata management through features such as crawling, querying, and data preview. It also ensures secure authentication via Credential Manager.

<figure><img src="/files/xJhYm4djBNSrOdUH0GlX" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                         | RDBMS       |
| -------------------------------------------------------------------------- | ----------- |
| OvalEdge Release Supported                                                 | Release8.1  |
| <p>Connectivity</p><p>\[How the connection is established with SQLite]</p> | JDBC driver |

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ❌      |
| Query Sheet                                  |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ❌      |
| Manual Lineage                               |       ❌      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ❌      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ❌      |

### Metadata Mapping

The following objects are crawled from SQLite and mapped to the corresponding UI assets.

<table><thead><tr><th width="193.44241333007812">SQLite Source Object</th><th width="155.8787841796875">SQLite Attribute</th><th width="171.0302734375">OvalEdge Attribute</th><th width="172.84857177734375">OvalEdge Category</th><th width="168.60595703125">OvalEdge Type</th></tr></thead><tbody><tr><td>Database</td><td>Default container</td><td>Container identifier</td><td>Container</td><td>Container</td></tr><tr><td>Tables</td><td>Table name</td><td>Table name</td><td>Table</td><td>Entity</td></tr><tr><td>Views</td><td>View name</td><td>View name</td><td>View</td><td>Entity </td></tr><tr><td>Indexes</td><td>Index identifier</td><td>Index identifier</td><td>Index</td><td>Index</td></tr><tr><td>Triggers</td><td>Trigger definition</td><td>Trigger definition</td><td>Trigger</td><td>Trigger</td></tr><tr><td>Columns</td><td>Column name and data type </td><td>Column name and type</td><td>Column</td><td>Column</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

#### **File Access**

Ensure the OvalEdge application environment has read access to the **SQLite** database file.

{% hint style="warning" %}
Provide a valid file path (e.g., /path/to/database.db). If the file is missing, locked, or inaccessible, connection validation and crawling will fail.\
For temporary use cases, :memory: can be used, but it is not persistent.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻 Who can provide these permissions? These permissions are typically granted by the SQLite administrator, as users may not have the required access to assign them independently.
{% endhint %}

| Operation                  | Objects                             | System Tables       | Access Permission               |
| -------------------------- | ----------------------------------- | ------------------- | ------------------------------- |
| Connection Validation      | Database file                       | sqlite\_master      | Ability to run validation query |
| Crawling                   | Tables / Views / Indexes / Triggers | sqlite\_master      | Read access                     |
| Query Sheet / Data Preview | Tables and Views                    | User tables / Views | Select                          |

### Connection Configuration Steps

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to **Administration > Connectors, click + (New Connector),** search for **SQLite**, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="219.5999755859375">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>SQLite</strong>" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SQLite connection              </p><p>(<strong>Example</strong>: "SQLite").</p></td></tr><tr><td>Connector description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Database file path*</td><td><p>Enter file path to the SQLite database file </p><p>(<strong>Example</strong>: /path/to/database.db). Use :memory: for an in-memory database</p></td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="238.79998779296875"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

### Manage Connector Operations

#### Crawl/Profile

{% hint style="info" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling.&#x20;

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the schemas to **crawl**.
3. The **Crawl** option is selected by default.
4. Click **Run** to collect metadata from the connected source and load it into the OvalEdge **Data Catalog**.
5. After a successful crawl, the information appears in the **Data Catalog > Databases/Tables/Table Columns tab**.

The **Schedule** checkbox allows automated crawling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the crawl operation at the scheduled time.

#### Other Operations

The **Connectors** page in the OvalEdge provides a centralized view of all configured connectors, including their health status.

**Managing connectors includes:**

* **Connectors Health:** Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing:** Click the **Eye** icon next to the connector name to view connector details, including databases, tables, columns, and codes.

**Nine Dots Menu Options:**

To view, edit, validate, configure, or delete connectors, click on the **Nine Dots menu**.

* **Edit Connector:** Update and revalidate the data source.
* **Validate Connector:** Check the connection's integrity.
* **Settings:** Modify connector settings.
  * **Crawler:** Configure data extraction.
  * **Query Policies:** Define query execution rules based on roles.
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Business Glossary Settings:** Manage term associations at the connector level.
* **Delete Connector:** Remove a connector with confirmation.

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="82.60003662109375">S.No.</th><th width="265.5999755859375">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Invalid connection config.</td><td><p><strong>Error Description:</strong> </p><ul><li>Required connection settings were missing during validation.</li></ul><p><strong>Resolution</strong>:</p><ul><li>Edit the connector settings.</li><li>Provide all mandatory fields.</li><li>Click Validate again.</li></ul></td></tr><tr><td>2</td><td>Database file path is required.</td><td><p><strong>Error Description:</strong> </p><ul><li>SQLite database file path was not provided.</li></ul><p><strong>Resolution</strong>:</p><ul><li>Enter a valid Database file path.</li><li>Ensure the file exists and is accessible.</li><li>Retry validation.</li></ul></td></tr><tr><td>3</td><td>Connection failed </td><td><p><strong>Error Description:</strong> </p><ul><li>Database connection or file access failed.</li></ul><p><strong>Resolution</strong>:</p><ul><li>Verify file path and permissions.</li><li>Ensure the database file is not locked or corrupted.</li><li>Retry validation.</li></ul></td></tr><tr><td>4</td><td>Failed to get fields</td><td><p><strong>Error Description:</strong> </p><ul><li>Metadata retrieval failed due to access or catalog issues.</li></ul><p><strong>Resolution</strong>:</p><ul><li>Ensure access to sqlite_master.</li><li>Verify SELECT access on tables/views.</li><li>Retry crawl.</li></ul></td></tr></tbody></table>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/rdbms/sqlite.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.