Infrastructure
Your warehouse, your SQL engine
EntiHub is built for Microsoft Fabric and Azure SQL first — the natural home for analytics-aligned MDM. The same product also runs on PostgreSQL, Oracle Database, and MySQL (or MariaDB), so you can align master data with the database your team already operates. One application; dialect-aware SQL for identifiers, paging, upserts, and timestamps — no forked product lines.
Supported database engines
- Microsoft SQL Server — Fabric Warehouse SQL endpoint, Azure SQL, SQL Server on-premises. Supports Microsoft Entra ID service principal or SQL authentication, matching how enterprises connect to Fabric today.
- PostgreSQL — Cloud or self-hosted. Connect with a standard database user; TLS options map to provider settings.
- Oracle — SQL*Net / Easy Connect style data source (host, port, service name). SQL user authentication.
- MySQL / MariaDB — MySQL protocol-compatible servers using SQL user authentication.
Same MDM capabilities
Backend choice does not strip features by itself. Entity YAML, deploy and redeploy, data API, approvals, permissions, audit, webhooks, packages, and CLI integration work the same — tier licensing (Small / Professional / Enterprise) still applies.
- Bootstrap creates configuration tables in your chosen config schema; entity tables land in your data schema.
- Deploy generates engine-appropriate DDL (types, indexes, views).
- Runtime queries use the right paging (
LIMIT/OFFSETvsOFFSET/FETCH), boolean literals, and upsert patterns per platform.
For operators
- Select the backend via configuration (
DatabaseBackend) and supply connection details or a full connection string. - Optional console prompt at startup lists all four engines for local development.
- Technical reference for settings and auth modes lives in the product repository:
docs/DATABASE-BACKENDS.md.