SQLite
Supported
Relational databases
Catalog SQLite database files: tables, views, columns, keys and indexes.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | The database file must be reachable from the Blindata Agent host (or attached to the connection as a file). |
| Keys, constraints & indexes | Supported | |
| Procedures & functions | Not available | |
| Data lineage | Partial | View definitions are available in sqlite_master and can be parsed by SQL lineage. |
| Lineage from query history | Not available | |
| Business glossary links | Supported | |
| Data quality probes | Supported | |
| Data profiling | Supported | |
| Data classification | Supported | |
| Chat with your data | Partial |
Connection settings
Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing SQLite in the technology step.
| Driver class | org.sqlite.JDBC |
|---|---|
| JDBC URL | jdbc:sqlite:database.db |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | JDBC |
The Blindata Agent does not include this driver: download the vendor JDBC driver and copy the .jar into the agent drivers folder, as described in
Add JDBC drivers.
Driver properties can be added under Advanced settings in the connection wizard.
Prerequisites & permissions
- A Blindata Agent installed with network access to SQLite.
- The vendor JDBC driver installed on the agent (see Add JDBC drivers).
- Read access to the database file from the agent host.
Set up metadata crawling
- Create the connection to SQLite on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents SQLite in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy JDBC.
- Run a TEST to check the number of extracted objects, then RUN or schedule the job.
The job options and the column aliases of every extraction query are described in the Generic JDBC reference.