![]() |
VOOZH | about |
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.
Accessing and integrating live data from Trino and Presto SQL engines has never been easier with CData. Customers rely on CData connectivity to:
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.
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.
π OLD DB Source, CData Presto Lookup and CData Presto DestinationsFollow the steps below to specify properties required to connect to the SQL Server instance.
Follow the steps below to save connection properties in the Connection Manager.
In the lookup component Transform Editor, define mappings from the SQL Server source table into the Presto lookup table.
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.
If the lookup component returns a match, update the existing record in Presto.
If the lookup component does not return a match, add a new record to Presto.
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.
π The completed upsert. (Salesforce is shown.)Download a free trial of the Presto SSIS Component to get started:
Download NowLearn more:
π Presto IconPowerful SSIS Source & Destination Components that allows you to easily connect SQL Server with Presto through SSIS Workflows.
Use the Presto Data Flow Components to synchronize with Presto Tables, and more. Perfect for data synchronization, local back-ups, workflow automation, and more!