Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Presto Data in RazorSQL
Connect to Presto from wizards and query Presto data from the GUI in the RazorSQL database management tool.
The CData JDBC Driver for Presto enables standards-based access from third-party tools, from wizards in IDEs to data management and analysis tools. This article shows how to connect to Presto using wizards in RazorSQL.
About Presto Data Integration
Accessing and integrating live data from Trino and Presto SQL engines has never been easier with CData. Customers rely on CData connectivity to:
- Access data from Trino v345 and above (formerly PrestoSQL) and Presto v0.242 and above (formerly PrestoDB)
- Read and write access all of the data underlying your Trino or Presto instances
- Optimized query generation for maximum throughput.
Presto and Trino allow users to access a variety of underlying data sources through a single endpoint. When paired with CData connectivity, users get pure, SQL-92 access to their instances, allowing them to integrate business data with a data warehouse or easily access live data directly from their preferred tools, like Power BI and Tableau.
In many cases, CData's live connectivity surpasses the native import functionality available in tools. One customer was unable to effectively use Power BI due to the size of the datasets needed for reporting. When the company implemented the CData Power BI Connector for Presto they were able to generate reports in real-time using the DirectQuery connection mode.
Getting Started
Create a JDBC Data Source for Presto Data
- Open the RazorSQL application and, in the Connections menu, select Add Connection Profile -> Other -> JDBC.
- In the Connection Wizard that appears, set the following properties:
- Driver Location: Set this property to the path to the lib subfolder in the installation directory.
- Driver Class: Set the driver class to cdata.jdbc.presto.PrestoDriver.
- Username: Enter the username. (This property can also be set in the JDBC URL.)
- Password: Enter the password. (This property can also be set in the JDBC URL.)
JDBC URL: Enter connection parameters. The JDBC URL begins with jdbc:presto: and is followed by a semicolon-separated list of connection properties.
Set the Server and Port connection properties to connect, in addition to any authentication properties that may be required.
To enable TLS/SSL, set UseSSL to true.
Authenticating with LDAP
In order to authenticate with LDAP, set the following connection properties:
- AuthScheme: Set this to LDAP.
- User: The username being authenticated with in LDAP.
- Password: The password associated with the User you are authenticating against LDAP with.
Authenticating with Kerberos
In order to authenticate with KERBEROS, set the following connection properties:
- AuthScheme: Set this to KERBEROS.
- KerberosKDC: The Kerberos Key Distribution Center (KDC) service used to authenticate the user.
- KerberosRealm: The Kerberos Realm used to authenticate the user with.
- KerberosSPN: The Service Principal Name for the Kerberos Domain Controller.
- KerberosKeytabFile: The Keytab file containing your pairs of Kerberos principals and encrypted keys.
- User: The user who is authenticating to Kerberos.
- Password: The password used to authenticate to Kerberos.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Presto JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.presto.jar
Fill in the connection properties and copy the connection string to the clipboard.
A typical JDBC URL is the following:
jdbc:presto:Server=127.0.0.1;Port=8080;

Query Presto Data and Select Tables
After establishing a connection, the wizard will close and the connection will be available in the connections panel. You can then query the tables.
