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 →Use the CData SSIS Components to Insert New or Update Existing Presto Records from SQL Server
Easily push SQL Server data to Presto using the CData SSIS Components. This example uses an SSIS workflow to either insert new records into Presto or update existing records with data from a SQL Server database.
SQL Server databases are commonly used to store enterprise records. It is often necessary to move this data to other locations. The CData SSIS Components for Presto allow you to easily transfer data from SQL Server to Presto.
This article demonstrates how to use the CData SSIS Components for Presto inside of a SQL Server Integration Services workflow to export data from SQL Server to Presto, utilizing a lookup component to find and update any existing records or insert new records.
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
Add the Components
To get started, add a new OLE DB source, CData Presto lookup, and two CData Presto destinations (one to handle a lookup with a match and one to handle a lookup without a match) to a new data flow task.

Configure the OLE DB Source
Follow the steps below to specify properties required to connect to the SQL Server instance.
- Open the OLE DB Source and add a new connection. Enter your server and database information here.
- In the Data access mode menu, select "Table or view" and select the table or view to export into Presto.
- Close the OLE DB Source wizard and connect it to the CData Presto Destination.
Create a New Connection Manager for Presto
Follow the steps below to save connection properties in the Connection Manager.
- Create a new Connection manager: In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
- In the Connection Manager type menu, select the CData Presto Connection Manager.
- Configure the connection properties. A typical Presto connection requires:
- User
- Password
- AccessToken
Configure the Presto Lookup
In the lookup component Transform Editor, define mappings from the SQL Server source table into the Presto lookup table.
- Double-click the Presto lookup to open the lookup component editor.
- In the Connection tab, select the Connection manager previously created.
- On the Connection tab, specify the Connection manager (or create a new one) and the table into which the data will be upserted. In this case, you will transfer Account records.
- On the Columns tab, configure the mapping of the primary key from the input columns to the primary key of the lookup columns.
Configure the Presto Destinations
Using the lookup component, you know which entries from the data source already exist in Presto and which ones are new. Configure two Presto components to handle the situation where a match is found and a match is not found.
Lookup Match Destination
If the lookup component returns a match, update the existing record in Presto.
- Map the Lookup Match Output to a Presto destination component.
- Double-click the Presto destination to open the destination component editor.
- In the Connection Manager tab, select the Connection manager previously created.
- Specify the table which will be updated and set the Action to "Update."
- On the Column Mappings tab, configure the mappings from the input columns to the destination columns (be sure to map the SQL Server primary key column to the Presto primary key column).
Lookup No Match Destination
If the lookup component does not return a match, add a new record to Presto.
- Map the Lookup No Match Output to a Presto destination component.
- Double-click the Presto destination to open the destination component editor.
- In the Connection Manager tab, select the Connection manager previously created.
- Specify the table into which the new record will be inserted and set the Action to "Insert."
- On the Column Mappings tab, configure the mappings from the input columns to the destination columns.
Run the Project
You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.
