diff --git a/modules/guides/images/connecting-power-bi/where-each-piece-runs.svg b/modules/guides/images/connecting-power-bi/where-each-piece-runs.svg new file mode 100644 index 000000000..5a7324d35 --- /dev/null +++ b/modules/guides/images/connecting-power-bi/where-each-piece-runs.svg @@ -0,0 +1,96 @@ + + Where each piece runs + Three zones: Microsoft's cloud, the customer's network and SDP on Kubernetes. Power BI Desktop runs on the analyst's PC with the Stackable ODBC driver and connector and connects to Trino. The Power BI Service in Microsoft's cloud connects to the on-premises data gateway in the customer's network, which has the Stackable ODBC driver and connector and connects to Trino. Power BI Report Server runs on the customer's Windows server, optionally with the Stackable ODBC driver, and connects to the Stackable PostgreSQL-to-Trino gateway, which connects to Trino. Trino is part of SDP; the Stackable ODBC driver, its connector and the Stackable PostgreSQL-to-Trino gateway are Stackable tools that are not part of SDP and are unsupported. + + + + + Part of SDP + + Stackable tool, not part of SDP, unsupported + + Microsoft + + + + + + Microsoft’s cloud + run by Microsoft + Customer’s network + Windows machines you run + SDP on Kubernetes + any data centre or cloud + + + + + + + + + + + Power BI Desktop + Windows application + on the analyst’s PC + + Stackable ODBC driver + and connector + for the ODBC route + + + Trino + on SDP + + + + Power BI Service + app.powerbi.com: reports + are published and viewed + + + On-premises data gateway + Windows service on + a customer machine + + Stackable ODBC driver + and connector + for the ODBC route + + + Trino + on SDP + + + + Power BI Report Server + server software on + your own Windows server + + Stackable ODBC driver + for import through ODBC + + + Stackable PostgreSQL- + to-Trino gateway + speaks PostgreSQL + + + Trino + on SDP + diff --git a/modules/guides/nav.adoc b/modules/guides/nav.adoc index e6de8ef38..301757ced 100644 --- a/modules/guides/nav.adoc +++ b/modules/guides/nav.adoc @@ -1,5 +1,6 @@ * xref:index.adoc[] ** xref:upgrading-sdp.adoc[] +** xref:connecting-power-bi.adoc[] ** xref:custom-images.adoc[] ** xref:debug-network-traffic.adoc[] ** xref:providing-resources-with-pvcs.adoc[] diff --git a/modules/guides/pages/connecting-power-bi.adoc b/modules/guides/pages/connecting-power-bi.adoc new file mode 100644 index 000000000..bcccdf243 --- /dev/null +++ b/modules/guides/pages/connecting-power-bi.adoc @@ -0,0 +1,137 @@ += Connecting Power BI to Trino +:description: Connect Power BI Desktop, the Power BI Service and Power BI Report Server to Trino on the Stackable Data Platform, using the Stackable ODBC driver or the Stackable PostgreSQL-to-Trino gateway. +:odbc-repo: https://github.com/stackabletech/stackable-odbc-trino +:odbc-releases: https://github.com/stackabletech/stackable-odbc-trino/releases +:pg-gateway-repo: https://github.com/stackabletech/postgresql-trino-gateway +:pg-gateway-chart: https://github.com/stackabletech/postgresql-trino-gateway/tree/main/deploy/helm/postgresql-trino-gateway +:ms-gateway-install: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install +:ms-gateway-custom: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-custom-connectors +:ms-gateway-sso: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-sso-overview +:ms-rs-sources: https://learn.microsoft.com/en-us/power-bi/report-server/data-sources +:ms-connector-announcement: https://community.fabric.microsoft.com/blog/fbc_pbiupdatesblog/empowering-our-customers-to-shape-the-future-of-data-connectivity-in-power-bi-an/5174038 + +This guide shows how each Microsoft Power BI product connects to Trino on the Stackable Data Platform (SDP). + +There are two ways to connect them: + +* the {odbc-repo}[Stackable ODBC driver for Trino{external-link-icon}^], which ships with a Power Query connector that adds *Stackable Trino* to the *Get Data* dialog, and +* the {pg-gateway-repo}[Stackable PostgreSQL-to-Trino gateway{external-link-icon}^], which runs in Kubernetes next to Trino and accepts PostgreSQL connections, so Power BI's built-in PostgreSQL connector can query Trino. + +[IMPORTANT] +==== +Both are open source, and neither is part of SDP. +Stackable support doesn't cover them. +If you need commercial support for either of them, https://stackable.tech/en/contact[contact us{external-link-icon}^]. +==== + +Which one you need, and where you install it, depends on the Power BI product you run. + +image::connecting-power-bi/where-each-piece-runs.svg["Where each piece runs: Microsoft's cloud, the customer's network and SDP on Kubernetes"] + +== Choose a route + +[NOTE] +==== +Power BI loads data in one of two modes. +Import copies the data into the Power BI model at each refresh, and reports query that copy. +DirectQuery leaves the data in Trino and sends a query to Trino for every report interaction. +==== + +[cols="2,3,3,4"] +|=== +|You run |Import |DirectQuery |You install + +|Power BI Desktop +|ODBC driver (recommended) or PostgreSQL-to-Trino gateway +|ODBC driver (recommended) or PostgreSQL-to-Trino gateway +a|Either + +* the ODBC driver and connector on the analyst's PC, or +* the PostgreSQL-to-Trino gateway in Kubernetes + +|Power BI Service (cloud) +|ODBC driver (recommended) or PostgreSQL-to-Trino gateway +|ODBC driver (recommended) or PostgreSQL-to-Trino gateway +a|Microsoft's on-premises data gateway on a Windows machine, and either + +* the ODBC driver and connector on that machine, or +* the PostgreSQL-to-Trino gateway in Kubernetes + +|Power BI Report Server +|ODBC driver or PostgreSQL-to-Trino gateway +|PostgreSQL-to-Trino gateway +a|Either + +* the ODBC driver on the Report Server, or +* the PostgreSQL-to-Trino gateway in Kubernetes +|=== + +Where both routes work, the ODBC driver is the recommended one, because the connector sends Trino SQL straight to Trino. +The PostgreSQL-to-Trino gateway adds a component in Kubernetes and has to rewrite the PostgreSQL that Power BI generates into SQL that Trino parses. + +Every route needs Trino reachable from the Windows machine that runs the Power BI component: the analyst's PC, the data gateway machine or the Report Server. +xref:trino:usage-guide/connect_to_trino.adoc[] covers the Trino side: endpoints, TLS and authentication. + +== Power BI Desktop + +Power BI Desktop is a Windows application on the analyst's PC. +It queries Trino directly from that PC, without Microsoft's cloud in the path. + +. Download the Windows archive from the {odbc-releases}[releases page{external-link-icon}^], unzip it and run `install.bat` as administrator. +. Copy `StackableTrinoODBC-.mez` into `%USERPROFILE%\Documents\Power BI Desktop\Custom Connectors\`. +. In *File > Options and settings > Options > Security*, allow any extension to load, then restart Power BI Desktop. +. Select *Get Data*, choose *Stackable Trino*, and enter the Trino coordinator's server, port and catalog. + +Each analyst connects with their own Trino credentials, or with Trino's browser login when *External authentication* is enabled in the connector's advanced options. + +To use the PostgreSQL-to-Trino gateway instead, deploy it as described in <> and connect with Power BI's built-in *PostgreSQL database* connector. + +== Power BI Service + +The Power BI Service runs in Microsoft's cloud and reaches Trino only through Microsoft's on-premises data gateway. +The data gateway is a Windows service that you install on a machine that can reach Trino. +The data gateway talks to both the Power BI Service and Trino, and passes queries and results between them. + +. {ms-gateway-install}[Install the on-premises data gateway{external-link-icon}^] on a Windows machine that can reach Trino. +. Install the Stackable ODBC driver on that machine, as for Power BI Desktop. +. Copy the `.mez` connector into a folder that the data gateway's service account can read, and select that folder under *Connectors* in the data gateway app. +. In the Power BI Service, enable custom connectors in the gateway cluster's settings and add a *Stackable Trino* data source with the credential Trino should see. + +{ms-gateway-custom}[Use custom data connectors with the on-premises data gateway{external-link-icon}^] covers the Microsoft side of steps 3 and 4. + +Every viewer's queries run as the data source's stored credential, so Trino's access rules see one user for all viewers. +Per-user restrictions have to be Power BI row-level security. +A DirectQuery model can use only one custom-connector data source, and Kerberos with Windows authentication isn't available for custom connectors through the data gateway. + +If the data gateway machine must not run custom connectors or third-party drivers, use the <> instead. +The data gateway's built-in PostgreSQL connector then needs no Stackable software on that machine. + +[WARNING] +.Single sign-on isn't available +==== +Power BI's {ms-gateway-sso}[single sign-on through the data gateway{external-link-icon}^], which runs each viewer's queries under their own identity, isn't available for Trino. +Microsoft enables it per connector in the Power BI Service and doesn't enable it for custom connectors such as *Stackable Trino*. +Since September 2025, Microsoft builds new connectors itself and no longer certifies connectors from partners ({ms-connector-announcement}[announcement{external-link-icon}^]). +==== + +== Power BI Report Server + +Power BI Report Server is server software on your own Windows server. +It queries Trino without Microsoft's cloud in the path. +It allows DirectQuery only for a {ms-rs-sources}[short list of data sources{external-link-icon}^] that includes PostgreSQL but not ODBC, and it doesn't refresh reports that use custom connectors. + +That's why Stackable built the <>: Report Server sees a PostgreSQL database and gets DirectQuery against Trino. + +* For import and DirectQuery, deploy the <> and use the built-in *PostgreSQL database* connector with user and password. +* For import only, install the Stackable ODBC driver on the Report Server, create a DSN for Trino with *ODBC Data Sources (64-bit)*, and use the built-in *ODBC* connector. + +[#postgresql-to-trino-gateway] +== PostgreSQL-to-Trino gateway + +The gateway runs in Kubernetes next to Trino and accepts PostgreSQL connections on port 5432. +It forwards queries to Trino and returns the results over the PostgreSQL protocol. +Most queries pass through unchanged, and the gateway rewrites the PostgreSQL constructs that Trino doesn't parse, such as `::` casts and `ILIKE`. +Install its Helm chart with the Trino coordinator's host and port, and make its Service reachable from the machine that runs the Power BI component. +{pg-gateway-chart}[The chart's README{external-link-icon}^] covers authentication and TLS. + +The gateway runs as a single replica, because a PostgreSQL cancel request has to reach the replica that holds the connection.