Supported Databases
Audience: IT and data teams
Goal: Choose supported database and warehouse connectors for PrismBI.
Databases and warehouses
PrismBI Edge Agents support read-only connectivity to common analytical and operational stores, including:
| System | Notes |
|---|---|
| MySQL | Operational reporting |
| PostgreSQL | Common OLTP and analytics |
| SQL Server (MSSQL) | Enterprise warehouse and OLTP |
| Oracle | Enterprise workloads |
| MongoDB | Document store |
| Neo4j | Graph database |
| DuckDB | Local analytical files |
| ClickHouse | High-volume analytics |
| Apache Pinot | Real-time OLAP |
| Elasticsearch | Search and log analytics |
Additional connector logos appear on the PrismBI marketing site as the platform expands—confirm availability with your account team before procurement.
Bundled vs. on-demand drivers
To keep the Edge Agent image free of restrictively-licensed packages, the standard image bundles SQLite, MySQL (PyMySQL), and DuckDB. Every other connector above is installed on demand from the Drivers tab the first time you need it. Installing a driver requires accepting its license—see Install database drivers.
Setup path
- Install the required driver on the Edge Agent and accept its license (Agents → <agent> → Drivers). See Install database drivers.
- Create a datasource in the Admin Portal.
- Run Test connection and Discover schema.
- Review entities in the Semantic catalog.
Security expectations
- Use read-only database roles with row and timeout limits enforced by PrismBI.
- Keep credentials in the customer network; rotate on your standard schedule.
- No inbound firewall rules from PrismBI cloud into your VPC are required.
Tips
- Match connector choice to where data already lives—PrismBI does not require centralizing data in the vendor cloud.
- Pilot with one warehouse before connecting every source.
- Document which datasource powers which business domain for Analyze users.
Troubleshooting
| Issue | What to try |
|---|---|
| Type not listed | Contact support for connector roadmap |
| Connection timeout | Check agent egress and database security groups |
| Schema incomplete | Re-run discovery; verify driver version on agent |