Menu
Integration Services (SSIS) supports reading data from OData sources. However, there is no OData destination component.
I cannot specify the OData webservice with an HTTP connection manager as web service task in SSIS (i.e. it does not support Windows Authentication).
Using Entity Framework/ASP.NET I think I could just write a post-deployment script. But is there a more straightforward way to update OData (if possible in SSIS)?
455
The Premium OData Source component is an SSIS data flow source component that can be used to read from OData endpoints. There are two pages that can be configured and worked with in the Premium OData Source component.
OData is a standard for building and consuming RESTful APIs. OData requests are made with a URL that uses HTTP to request data, using the returned data to populate the report. A Universal Resource Identifier (URI) looks just like a URL and is the connection point for an OData service.
I don't think there is an ODATA Destination component created by Microsoft. You can find ODATA Source and create an ODATA connections only. (In SQL Server 2014 you have to install it from the feature pack, in 2016+ it is included).
On the other hand, there is some third party components that you can find in Visual Studio Marketplace:
There was a feature request on Visual Studio website to support ODATA Destination, and it was closed.
134
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
