![]() |
VOOZH | about |
This article illustrates using the Strava ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Strava data 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.
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 Strava data.
To authenticate to Strava, and connect to your own data or to allow other users to connect to their data, you can use the OAuth standard.
You must create a custom OAuth application to connect to Strava. To create a custom OAuth application:
After setting the following connection properties, you are ready to connect:
Profile=C:\profiles\Strava.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackURL=http://localhost:33333;👁 Connection properties in the Connection Manager dialog. (Salesforce is shown.)
Open the DataReader editor and set the following information:
SELECT , FROM Athlete WHERE = ''
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.Connect to live data from Strava with the API Driver
Connect to Strava