How to integrate Trino with Power BI

Learn how to quickly and efficiently connect Trino with Power BI for smooth data access.

Read and write Trino data effortlessly. Query, analyze, and integrate catalogs and data from multiple sources — almost no coding required. You can do it all using the high-performance Trino ODBC Driver for Power BI (often referred to as the Trino Connector). We'll walk you through the entire setup.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Video Tutorial

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

• How to download and install the required PowerPack for Trino integration in Power BI
• How to configure the connection for Trino
• Features of the ZappySys JDBC Bridge Driver (Authentication / Query Language / Examples / Driver UI)
• How to use the Trino in Power BI

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

• Minimum required version: Java 11
  • Amazon Corretto 11
  • Oracle JRE 11
• Recommended Java version: Java 21
  • Amazon Corretto 21
  • Oracle JRE 21

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

Download Trino JDBC driver

To connect to Trino in , you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

1. Visit Trino official website.
2. Download the JDBC driver, and save it locally, e.g. to D:\Drivers\JDBC\trino-jdbc.jar.
3. Done! That was easy, wasn't it? Let's proceed to the next step.

Create data source using Trino ODBC Driver

Step-by-step instructions

To get data from Trino using Power BI, we first need to create an ODBC data source. We will later read this data in Power BI. Perform these steps:

1. Download and install ODBC PowerPack (if you haven't already).

2. Search for odbc and open the ODBC Data Sources (64-bit):

   

3. Create a User data source (User DSN) based on the ZappySys JDBC Bridge Driver driver:

   ZappySys JDBC Bridge Driver

   
   • Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
   • Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this
   When deployed to production, Power BI runs under a Service Account. Therefore, for the production environment, you must create and use a System DSN.

4. Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

   TrinoDSN

   jdbc:trino://trino-instance-host-name:8080

   D:\Drivers\JDBC\trino-jdbc.jar

   admin

   ****************

   []

   

   Use these values when setting parameters:

   • Connection string: jdbc:trino://trino-instance-host-name:8080
   • JDBC driver file(s): D:\Drivers\JDBC\trino-jdbc.jar
   • User name: admin
   • User password: ****************
   • Connection parameters: []

5. You should see a message saying that connection test is successful:

   

   Otherwise, if you are getting an error, check out our Community for troubleshooting tips.

6. We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:

   TrinoDSN

   SELECT * FROM tpch.sf1.orders

   

   SELECT * FROM tpch.sf1.orders

   You can also click on the <Select Table> dropdown and select a table from the list.

   The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the Bridge Driver simply relays the SQL query without altering it.

   Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.

7. Click OK to finish creating the data source.

Video Tutorial

Connect to Trino data in Power BI

Import data from a table or view

1. Once you open Power BI Desktop click Get Data to get data from ODBC:

   

2. A window opens, and then search for "odbc" to get data from ODBC data source:

   

3. Another window opens and asks to select a Data Source we already created. Choose TrinoDSN and continue:

   TrinoDSN

   

4. Most likely, you will be asked to authenticate to a newly created DSN. Just select Windows authentication option together with Use my current credentials option:

   TrinoDSN

   

5. Finally, you will be asked to select a table or view to get data from. Select one and load the data!

   

6. Finally, finally, read extracted data from Trino in a Power BI report:

   

Import data using a SQL query

If you wish to import Trino data from SQL query rather than a table then you can use advanced options during import steps (as below). After selecting DSN you can click on advanced options to see SQL Query editor.

TrinoDSN

SELECT * FROM tpch.sf1.orders

Publish Power BI report to Power BI service

Here are the instructions on how to publish a Power BI report to Power BI service from Power BI Desktop application:

1. First of all, go to Power BI Desktop, open a Power BI report, and click Publish button:

   

2. Then select the Workspace you want to publish report to and hit Select button:

   

3. Finally, if everything went right, you will see a window indicating success:

   

What's next? If you need to periodically refresh Power BI semantic model (dataset) to ensure data accuracy and up-to-dateness, you can accomplish that by using Microsoft On-premises data gateway. Proceed to the next section - Refresh the Power BI semantic model via the gateway - and learn how to do that.

Refresh the Power BI semantic model (dataset) via the gateway

Power BI allows you to refresh semantic models (previously known as "datasets") that are based on data sources residing on-premises. This is achieved using the Microsoft On-premises data gateway. It acts as a secure bridge between Power BI cloud services and your local Trino ODBC data source:

There are two types of On-premises data gateways:

You can download the On-premises data gateway directly from the Microsoft Fabric or Power BI portals:

Below are instructions on how to refresh the semantic model using both gateway types.

Use the Standard mode gateway (recommended)

Best for enterprise production environments where multiple users need to share the same gateway connection.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Standard mode):

1. Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:

   

2. If you see this view, it means you must install the On-premises data gateway (Standard mode):

   

3. Download On-premises data gateway (standard mode) and run the installer.

4. Once the configuration window opens, sign in:

   
   Sign in with the same email address you use for Microsoft Fabric.

5. Select Register a new gateway on this computer (or migrate an existing one):

   

6. Name your gateway, enter a Recovery key, and click the Configure button:

   
   Save your Recovery Key in a safe place (like a password manager). If you lose it, you cannot restore or migrate this gateway later.

7. Once Microsoft gateway is installed, check if it registered correctly:

   • Go back to Power BI portal

   • Click Gear icon on top-right

   • And then hit Manage connections and gateways menu item

   

8. Continue by clicking the On-premises data gateway tab and selecting Standard mode gateways from the dropdown menu:

   

   If your gateway is not listed, the registration may have failed. To resolve this:

   • Wait a couple of minutes and refresh Power BI portal page
   • Restart the machine where On-premises data gateway is installed
   • Check firewall settings

9. Success! The gateway is now Online and ready to handle requests.

10. Now, return to your semantic model settings in the Power BI portal. Refresh the page, and you should see your newly created gateway. Click the arrow icon to expand the options, and then click the Add to gateway link:

    ODBC{"connectionstring":"dsn=TrinoDSN"}

    

11. Once you do that, you will create a new gateway connection. Give it a name, set the Authentication method, Privacy level, and click the Create button:

    dsn=TrinoDSN

    
    In this example, we use the least restrictive Privacy level.

    If your connection uses a full connection string, you may hit a length limitation when entering it into the field. To create the connection, you will need to shorten it manually. Check the section about the limitation of a full connection string on how to accomplish this.

    On-premises data gateway (Personal mode) does not have this limitation.

12. Select the newly created connection to map it to your dataset:

    ODBC{"connectionstring":"dsn=TrinoDSN"}

    

13. Finally, you can refresh the semantic model:

    

Use the Personal mode gateway (POC)

Best for single-user scenarios, quick tests (POC), or when you don't have administrative rights to install the Standard gateway.

Follow these steps to refresh a Power BI semantic model using the On-premises data gateway (Personal mode):

1. Go to Power BI My workspace, hover your mouse cursor over your semantic model, and click Settings:

   

2. If you see this view, it means you must install the On-premises data gateway (Personal mode):

   

3. Install On-premises data gateway (personal mode) and sign-in:

   
   Use the same email address you use when logging in into your account.

4. Once Microsoft gateway is installed, check if it registered correctly:

   • Go back to Power BI portal

   • Click Gear icon on top-right

   • And then hit Manage connections and gateways menu item

   

5. Continue by clicking On-premises data gateway tab and select Personal mode option from the dropdown:

   

   If your gateway is not listed, the registration may have failed. To resolve this:

   • Wait a couple of minutes and refresh Power BI portal page
   • Restart the machine where On-premises data gateway is installed
   • Check firewall settings

6. The On-premises data gateway is now Online and ready to receive requests.

7. Return to your semantic model Settings, expand Data source credentials, click Edit credentials, select the Authentication method and the Privacy level, and then click the Sign in button:

   dsn=TrinoDSN

   

8. Finally, you are ready to refresh your semantic model:

   

Advanced topics

Editing query in Power BI

There will be a time you need to change the initial query after importing data into Power BI. Don't worry, just right-click on your table and click Edit query menu item:

Using parameters for dynamic queries

In the real world, many values of your REST / SOAP API call may be coming from parameters. If that's the case for you can try to edit script manually as below. In below example its calling SQL Query with POST method and passing some parameters. Notice below where paraAPIKey is Power BI Parameter (string type). You can use parameters anywhere in your script just like the normal variable.

To use a parameter in Power BI report, follow these simple steps:

1. Firstly, you need to Edit query of your table (see previous section)

2. Then just create a new parameter by clicking Manage Parameters dropdown, click New Parameter option, and use it in the query:

                   
                               = Odbc.Query("dsn=TrinoDSN",
                                            "SELECT ProductID, ProductName, UnitPrice, UnitsInStock
                                             FROM Products
                                             WHERE UnitPrice > " & Text.From(MyParameter) & "
                                             ORDER BY UnitPrice")
                           
                   

   
   Refer to Power Query M reference for more information on how to use its advanced features in your queries.

Using DirectQuery (live connection)

By default, Power BI imports Trino data into its internal cache. However, if you require real-time data, you can use the DirectQuery mode.

Since the native Power BI ODBC connector limits you to Import mode, we must bridge the connection via Microsoft SQL Server. To do this, we configure the ZappySys Data Gateway and create a Linked Server pointing to it:

Follow these steps to use DirectQuery:

1. Configure ZappySys Data Gateway and create a Linked Server in SQL Server.

2. Once the Linked Server is ready, open Power BI Desktop.

3. Click Get Data and select SQL Server.

4. Enter your SQL Server instance name and a valid database name (e.g., master).

5. Under Data Connectivity mode, select DirectQuery.

6. Expand Advanced options and enter your SQL query using the OPENQUERY syntax below (replace [LINKED_SERVER_NAME] with your actual Linked Server name):

   SELECT * FROM OPENQUERY([LS_TO_TRINO_IN_GATEWAY], 'SELECT * FROM tpch.sf1.orders')

   

   SELECT * FROM OPENQUERY([LS_TO_TRINO_IN_GATEWAY], 'SELECT * FROM tpch.sf1.orders')

7. Click OK and load the data. Your Trino data is now linked live rather than imported.

Using full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

1. Open ODBC data source configuration and click Copy settings:
   

   ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

   ZappySys JDBC Bridge Driver - Trino

   Read and write Trino data effortlessly. Query, analyze, and integrate catalogs and data from multiple sources — almost no coding required.

   TrinoDSN

   
2. The window opens, telling us the connection string was successfully copied to the clipboard:
3. Then just paste the connection string into your script:
   TrinoDSN

   DRIVER={ZappySys JDBC Bridge Driver};JdbcConnectionString='jdbc:trino://trino-instance-host-name:8080';ClassName='';DriverPath='D:\Drivers\JDBC\trino-jdbc.jar';UserName='admin';UserPassword='****************';ConnParams='[]'

   
4. You are good to go! The script will execute the same way as using a DSN.

Handling limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols (or sometimes more). It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If you are using such a long ODBC connection string, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the full connection string in a file. Follow the steps below to achieve this:

1. Open your ODBC data source.
2. Click Copy settings button to copy a full connection string (see the previous section on how to accomplish that).
3. Then create a new file, let's say, in C:\temp\odbc-connection-string.txt.
4. Continue by pasting the copied connection string into a newly created file and save it.
5. Finally, the last step! Just construct a shorter ODBC connection string using this format:

   DRIVER={ZappySys JDBC Bridge Driver};SettingsFile=C:\temp\odbc-connection-string.txt

6. Our troubles are over! Now you should be able to use this connection string in Power BI with no problems.

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Trino data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

• Centralized data access
  The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
• Centralized access control
  Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in Power BI (client-side) to connect to it.

Let's not wait and get going!

Create Trino data source in the gateway

In this section we will create a data source for Trino in the Data Gateway. Let's follow these steps to accomplish that:

1. Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:

   

2. Go to the Users tab and follow these steps to add a Data Gateway user:

   • Click the Add button
   • In the Login field enter a username, e.g., john
   • Then enter a Password
   • Check the Is Administrator checkbox
   • Click OK to save
   

3. Now we are ready to add a data source:

   • Click the Add button
   • Give the Data source a name (have it handy for later)
   • Then select Native - ZappySys JDBC Bridge Driver
   • Finally, click OK
   TrinoDSN

   ZappySys JDBC Bridge Driver

   

4. When the ZappySys JDBC Bridge Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Trino ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:

   • Open ODBC data source configuration and click Copy settings:
     

     ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

     ZappySys JDBC Bridge Driver - Trino

     Read and write Trino data effortlessly. Query, analyze, and integrate catalogs and data from multiple sources — almost no coding required.

     TrinoDSN

     
   • The window opens, telling us the connection string was successfully copied to the clipboard:

   • Then go to Data Gateway configuration and in data source configuration window click Load settings:

     TrinoDSN

     

     ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]

     ZappySys JDBC Bridge Driver - Trino

     Read and write Trino data effortlessly. Query, analyze, and integrate catalogs and data from multiple sources — almost no coding required.

     TrinoDSN

     
   • Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.

5. Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:

   
   • This will initially allow all inbound traffic.
   • Click Edit IP filters to restrict access to specific IP addresses or ranges.

6. Crucial Step: After creating or modifying the data source, you must:

   • Click the Save button to persist your changes.
   • Hit Yes when prompted to restart the Data Gateway service.

   This ensures all changes are properly applied:

   
   Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from Power BI. To achieve that, let's perform these steps:

1. Search for odbc and open the ODBC Data Sources (64-bit):

   

2. Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

   ODBC Driver 17 for SQL Server

   
   If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.

3. Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

   ZappySysGatewayDSN

   localhost,5000

   
   Make sure you separate the hostname and port with a comma, e.g. localhost,5000.

4. Proceed with the authentication part:

   • Select SQL Server authentication
   • In the Login ID field enter the user name you created in the Data Gateway, e.g., john
   • Set Password to the one you configured in the Data Gateway
   

5. Then set the default database property to TrinoDSN (the one we used in the Data Gateway):

   TrinoDSN

   TrinoDSN

   
   Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).

6. Continue by checking the Trust server certificate option:

   

7. Once you do that, test the connection:

   

8. If the connection is successful, everything is good:

   

9. Done!

We are ready to move to the final step. Let's do it!

Access data in Power BI via the gateway

Finally, we are ready to read data from Trino in Power BI via the Data Gateway. Follow these final steps:

1. Go back to Power BI.

2. Once you open Power BI Desktop click Get Data to get data from ODBC:

   

3. A window opens, and then search for "odbc" to get data from ODBC data source:

   

4. Another window opens and asks to select a Data Source we already created. Choose ZappySysGatewayDSN and continue:

   ZappySysGatewayDSN

   

5. When the ODBC driver authentication window opens, configure the following:

   • Enter the User name (e.g., john)
   • Enter the Password that you configured in ZappySys Data Gateway
   • Hit the Connect button
   dsn=ZappySysGatewayDSN

   
   Make sure the Database tab is selected; otherwise, Power BI won't be able to connect to the ZappySys Data Gateway.

6. Read the data the same way we discussed at the beginning of this article.

7. That's it!

Now you can connect to Trino data in Power BI via the Data Gateway.

Troubleshooters & resources (JDBC Bridge Driver)

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

• How to combine multiple JAR files
  Learn how to merge multiple .jar dependencies when your JDBC driver requires more than one file.
• How to fix JBR error: “Data lake is not available / Unable to verify trust for server certificate chain”
  Resolve SSL or certificate validation issues encountered during JDBC connections.
• System Exception: “Java is not installed or not accessible”
  Fix Java path or environment issues that prevent the JDBC Bridge from launching Java.
• JDBC Bridge Driver disconnect from Java host error
  Troubleshoot unexpected disconnection problems between SSIS and the Java process.
• Error: Could not open jvm.cfg while using JDBC Bridge Driver
  Resolve JVM configuration path errors during driver initialization.
• How to enable JDBC Bridge Driver logging
  Enable detailed driver logging for better visibility during troubleshooting.
• How to pass JDBC connection parameters (not by URL)
  Learn how to specify connection properties programmatically instead of embedding them in the JDBC URL.
• How to fix JDBC Bridge error: “No connection could be made because the target machine actively refused it”
  Troubleshoot firewall or local port binding issues preventing communication with the Java host.
• How to use JDBC Bridge options (System Property for Java command line, e.g., classpath, proxy)
  Configure custom Java options like classpath and proxy using JDBC Bridge system properties.

Conclusion

In this article we showed you how to connect to Trino in Power BI and integrate data without writing complex code — all of this was powered by Trino ODBC Driver. It's worth noting that ZappySys JDBC Bridge Driver allows you to connect not only to Trino, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

Download ODBC PowerPack now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

Explore Power BI connectors

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Azure DevOps

Cosmos DB

Dropbox

DuckDB (Parquet)

ElasticSearch

FastSpring

Gmail

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Search Console

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManageEngine ServiceDesk Plus (Zoho)

MariaDB

MySQL

Neo4j

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

More Trino integrations

SSIS

SQL Server

Microsoft Fabric

SSRS

Informatica PowerCenter

MS Access

Excel

SSAS

C#

Python

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

Alteryx

ODBC