Connect ParadeDB (PostgreSQL-compatible) to Microsoft Power BI using the built-in PostgreSQL connector or Npgsql.
Power BI turns ParadeDB’s transactional data into interactive dashboards without data exports. DirectQuery keeps visuals live; Import boosts speed for static reports.
• ParadeDB running and reachable on port 5432.
• A read-only PostgreSQL user.
• SSL certificate if remote.
• Latest Npgsql provider (≥5.0) installed on the workstation.
Edit postgresql.conf
to set listen_addresses = '*'
; update pg_hba.conf
with:hostssl all powerbi_user 0.0.0.0/0 md5
. Restart ParadeDB: sudo systemctl restart paradedb
.
Use Power BI’s “PostgreSQL database” connector or “ODBC” if Npgsql isn’t detected. Example string:
Server=parade-prod.acme.com;Database=ecommerce;Port=5432;User Id=powerbi_user;Password=$ecret;SSL Mode=Require;
1. Home → Get Data → Database → PostgreSQL.
2. Enter server & database; choose DirectQuery or Import.
3. Click “Advanced options” to paste custom SQL if desired.
4. Select authentication → Database; supply credentials; connect.
After connection, Navigator shows tables. Choose “Orders”. In the Power Query editor, open “Advanced Editor” and paste the example query below to confirm data retrieval.
• Grant read-only roles.
• Use views to simplify complex joins.
• Index filter columns to accelerate DirectQuery.
• Schedule data-refresh windows during off-peak hours.
• Error "provider not found" → install Npgsql.
• Error 28000 → verify pg_hba.conf
order.
• Timeout → check firewall or VPN split-tunnel.
Create a schema bi
, move approved views into it, and revoke usage on others:REVOKE ALL ON SCHEMA public FROM powerbi_user;
GRANT USAGE ON SCHEMA bi TO powerbi_user;
Yes. Configure an On-Premises Data Gateway pointing to ParadeDB and replicate the same connection string used in Desktop.
DirectQuery works but performance depends on indexing and network latency. Consider Import for heavy aggregations.
Power BI defaults to SSL if the server supports it. Set SSL Mode=Require
to enforce encrypted traffic.