Postgres & Clickhouse Data Sources Not Appearing for Scheduled Refresh using Standard Mode Gateway

[Divyanshu15]

Hello Community,

I’m encountering an issue with the Standard mode gateway in Microsoft Fabric / Power BI Service.

I have two data sources — PostgreSQL and ClickHouse — connected successfully in Power BI Desktop. After publishing the report to the Power BI Service, I connected the workspace to the Standard mode gateway. However, the issue is that these two data sources do not appear under the “Gateway connection” section for scheduled refresh, even though the gateway is online and configured correctly.

A few details about my setup:

• Gateway type: Standard mode

• Data sources: PostgreSQL and ClickHouse

• Connection status in Desktop: Successful

• Power BI Service issue: Data sources not visible for mapping under Gateway connection

• What works: Personal mode gateway connects and refreshes successfully

• Limitation: Since I have two different environments, I cannot rely on Personal mode gateway (as only one is allowed per tenant)

Thank you for your time and guidance!

Best 

Divy

[v-ssriganesh · Accepted solution]

Hello @Divyanshu15,
Thank you for posting your query in the Microsoft Fabric Community Forum.

For PostgreSQL (natively supported), go to Settings > Manage connections and gateways > your gateway > Add data source > select PostgreSQL > enter server/database/credentials and create it. For ClickHouse, first install the ClickHouse ODBC driver on the gateway server, create a System DSN in ODBC Administrator, then add it via ODBC data source type using that DSN name and credentials. Once added, return to your dataset Settings > Gateway connection to map them, enable scheduled refresh, and test. Ensure server names match exactly what you used in Desktop.

if issues persist, check gateway diagnostics or update to the latest version. This setup will handle your multi-environment needs perfectly

Best regards,
Ganesh Singamshetty.

[v-ssriganesh]

Hello @Divyanshu15,

Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.

Thank you.

[v-ssriganesh]

Hello @Divyanshu15,

We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.

Thank you.

[SolomonovAnton · Accepted solution]

In the Power BI Service, the Gateway connection section appears only when every on-premises source used by the semantic model has a matching data source entry on the selected gateway with the exact same connection details (server/DB for native connectors; DSN/connection string for ODBC/custom), and the gateway has the required drivers/connectors installed. Otherwise it simply won’t list anything to map. 

---

1) Create matching data sources on the Standard gateway

1. PostgreSQL (native connector):
   • Go to Manage connections and gateways → Gateways → <your cluster> → Add data source.
   • Choose PostgreSQL. Enter Server and Database exactly as used by your PBIX (avoid “localhost”/“127.0.0.1”; use the hostname reachable from the gateway network; include the port if non-default, e.g., myhost:5433).
   • Set credentials and Privacy level. Add yourself/owners under Users.
   • Recent gateway builds already include the Npgsql provider; no separate install is needed unless you override versions. 
2. ClickHouse:
   • If you’re using the ClickHouse connector in Power BI (now GA), it relies on the ClickHouse ODBC driver. Install the 64-bit ClickHouse ODBC driver on the gateway machine. 
   • If you connected via ODBC in Desktop, add a data source of type ODBC on the gateway:
     • Install the same ODBC driver on the gateway.
     • Create a System DSN (if Desktop used DSN). Then, in the gateway, set the ODBC connection to DSN=YourClickHouseDSN; or paste the exact driver connection string you used in Desktop. DSN and driver strings are both supported. 
   • ClickHouse’s official guidance covers using ODBC with Power BI and the gateway. 

Important: The dataset will only surface the gateway for mapping after both sources (PostgreSQL + ClickHouse) have valid entries on the same gateway cluster. If even one is missing/mismatched, the list is empty. 

---

2) Make the Desktop ↔ Gateway details identical

• Server/DB/Port must match byte-for-byte for PostgreSQL. If you parameterized server/database in Power Query, the Service will expect to map those parameters—values must match what the gateway entry uses. 
• ODBC exactness: For ClickHouse/ODBC, the gateway compares the entire connection string/DSN. Keep the same DSN name or copy the literal connection string from Desktop to the gateway data source. 
• Ensure Privacy levels on the gateway data sources match the model’s intent (especially if you’re combining sources).

---

3) If you used a custom connector (.mez)

• Place the .mez file in the gateway’s custom connectors folder and enable “Allow user’s custom data connectors” for the gateway cluster; restart the gateway service. Use the same connector version in Desktop and on the gateway. 

---

4) Check whether a gateway is even required

• If your PostgreSQL is an internet-reachable cloud database (e.g., Azure Database for PostgreSQL) and you use the cloud connector, you may not need a gateway—the Service could use a cloud connection or VNet Data Gateway instead; in that case, the Gateway mapping section won’t appear. 

---

5) Quick diagnostics checklist

• Gateway status = Online and you’re an admin or user of the gateway.
• Under Manage connections and gateways, you can see:
  • Data source “PostgreSQL — <server> / <db>” (auth OK).
  • Data source “ODBC — DSN=YourClickHouseDSN” (or exact ClickHouse driver string) (auth OK).
• Open the dataset (semantic model) settings → Data source credentials (no errors) → Gateway connection now shows the gateway cluster and both sources mapped.
• Drivers present on gateway host: Npgsql (bundled) for PostgreSQL; ClickHouse ODBC driver x64 for ClickHouse. 
• No use of localhost / 127.0.0.1 in Desktop connections.

---

Typical root causes (and the fixes)

1. Never added the gateway data sources (only installed the gateway).
   Fix: Add both sources on the gateway with matching details. 
2. Mismatched connection details (e.g., Desktop uses myhost:5432, gateway uses myhost only; DSN name differs).
   Fix: Align server:port/DB for PostgreSQL; make DSN/connection string identical for ODBC. 
3. Missing ODBC driver on gateway for ClickHouse.
   Fix: Install ClickHouse ODBC driver x64 on the gateway. 
4. Used a custom connector in Desktop but not enabled/installed on gateway.
   Fix: Deploy .mez to gateway and enable custom connectors on the cluster; restart. 
5. Source doesn’t need a gateway (cloud path), so mapping section stays hidden.
   Fix: Use a cloud connection or VNet gateway path instead of Standard gateway for that source. 

---

Reference setup links

• On-premises data gateway (Standard) overview. 
• Gateway troubleshooting & mapping behavior. 
• PostgreSQL connector (cloud, VNet, on-prem gateway; Npgsql notes).
• ClickHouse connector (GA) and ODBC driver requirement. 
• ClickHouse + Power BI integration guides (ODBC). 
• ODBC with gateway (DSN/driver string support). 

---

Next steps to validate

1. Add both data sources to the Standard gateway as above.
2. Open the semantic model in the Service → Settings → confirm the gateway appears and both sources map automatically. If parameters are used, map them in the gateway section.
3. Run Refresh now. Check the Refresh history for any driver/credential errors and share the exact message if anything fails.

✔️ If my message helped solve your issue, please mark it as Resolved!

👍 If it was helpful, consider giving it a Kudos!

[tayloramy]

Hi @Divyanshu15,

Before the connections show up in the gateway, they need to be created. 

Postgres is natively supported, so you will be able to create a postgres connection easily. 

For ClickHouse, I think you will need to use an ODBC connection as there is no native connection. This is a bit more work and requires some setup to be done on the gateway server. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

[v-ssriganesh · Accepted solution]

Hello @Divyanshu15,
Thank you for posting your query in the Microsoft Fabric Community Forum.

For PostgreSQL (natively supported), go to Settings > Manage connections and gateways > your gateway > Add data source > select PostgreSQL > enter server/database/credentials and create it. For ClickHouse, first install the ClickHouse ODBC driver on the gateway server, create a System DSN in ODBC Administrator, then add it via ODBC data source type using that DSN name and credentials. Once added, return to your dataset Settings > Gateway connection to map them, enable scheduled refresh, and test. Ensure server names match exactly what you used in Desktop.

if issues persist, check gateway diagnostics or update to the latest version. This setup will handle your multi-environment needs perfectly

Best regards,
Ganesh Singamshetty.