![]() |
VOOZH | about |
This article illustrates using the OData ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of OData services to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.
CData simplifies access and integration of live OData services data. Our customers leverage CData connectivity to:
Customers use CData's solutions to regularly integrate their OData services with preferred tools, such as Power BI, MicroStrategy, or Tableau, and to replicate data from OData services to their databases or data warehouses.
In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.
๐ The components used in the data task in this example.In the connection manager, enter the connection details for OData services.
The User and Password properties, under the Authentication section, must be set to valid OData user credentials. In addition, specify a URL to a valid OData server organization root or OData services file.
๐ Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT Orders.Freight, Customers.ContactName FROM Customers INNER JOIN Orders ON Customers.CustomerId=Orders.CustomerId
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
๐ Input and destination columns in the OLE DB Destination Editor.Download a free trial of the OData Data Provider to get started:
Download NowLearn more:
๐ OData IconEasy-to-use OData client (consumer) enables developers to build .NET applications that easily communicate with OData services.