Veeva Vault connector
This feature is in Beta.
The managed Veeva Vault connector in Lakeflow Connect ingests standard objects (__v), custom objects (__c), system tables, and audit trail tables from Veeva Vault into Databricks. The connector uses Veeva's Direct Data API to access your Vault instance.
Feature availability
Feature | Availability |
|---|---|
UI-based pipeline authoring |
|
API-based pipeline authoring |
|
Declarative Automation Bundles |
|
Incremental ingestion |
|
Unity Catalog governance |
|
Orchestration using Databricks Workflows |
|
API-based column selection and deselection |
|
API-based row filtering |
|
SCD Type 2 |
|
Automated schema evolution: New and deleted columns |
|
Automated schema evolution: Data type changes |
|
Automated schema evolution: Column renames |
Requires a full refresh. |
Authentication methods
Authentication method | Availability |
|---|---|
OAuth U2M |
|
OAuth M2M (Microsoft Entra ID) |
|
Basic authentication (username/password) |
|
Ingest from Veeva Vault in 3 steps
Before starting, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
- Configure Veeva Vault for ingestion (Admins) — Set up Veeva Vault to authenticate with Databricks.
- Create a Unity Catalog connection (Admins) — Create a connection in Catalog Explorer so non-admins can create pipelines.
- Create an ingestion pipeline (Admins or non-admins) — Select any supported interface and create a pipeline from an existing connection.