External database connections let ActiveManage read from (and optionally write to) databases that aren't part of the platform's own storage — legacy systems, data warehouses, partner databases, analytics stores.
Supported Engines
- MySQL / MariaDB — full read/write.
- PostgreSQL — full read/write.
- SQL Server — read/write via ODBC.
- Oracle — read/write via OCI.
- SQLite — read-only by default.
- Snowflake / BigQuery / Redshift — read-only analytics access.
Connection Settings
- Hostname, port — direct or through a tunnel.
- Authentication — password, certificate, IAM role.
- SSL/TLS — always enable for production connections.
- Read-only toggle — refuses to send any non-SELECT statement.
- Connection pool size — how many simultaneous connections to maintain.
- Query timeout — kill slow queries automatically.
Step-by-Step
- Open Architect Panel → External Databases and click Add Connection.
- Pick the engine and provide credentials.
- Click Test connection — the platform makes a sample SELECT.
- Pick whether this connection is read-only.
- Configure pool and timeout.
- Save and assign to the relevant datastores or queries.
Worked Examples
- Legacy ERP read: Read-only MySQL connection to the on-prem ERP, used to display order history in the customer service screen.
- Data warehouse: Read-only Snowflake connection used by the reporting engine for big aggregations.
- Multi-write integration: PostgreSQL connection to a third-party billing system; ActiveManage writes invoice records on creation and reads payment status periodically.
- Analytics-only: BigQuery connection used by the dashboards for time-series customer behaviour.
Warning: Never use the same DB credentials for the platform's own storage and an external connection. Compromise of one shouldn't grant access to the other.