Microsoft Access
Supported
Relational databases
Catalog Microsoft Access .mdb and .accdb files with the open-source UCanAccess JDBC driver.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | Install the UCanAccess driver JARs in the agent drivers folder; the Access file must be reachable from the agent host. |
| Keys, constraints & indexes | Supported | |
| Procedures & functions | Not available | |
| Data lineage | Not available | |
| 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 JDBC (generic) in the technology step.
| Driver class | net.ucanaccess.jdbc.UcanaccessDriver |
|---|---|
| JDBC URL | jdbc:ucanaccess://C:/data/mydb.accdb |
| 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 Microsoft Access.
- The vendor JDBC driver installed on the agent (see Add JDBC drivers).
- Read access to the Access file from the agent host.
Set up metadata crawling
- Create the connection to Microsoft Access on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Microsoft Access 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.