![]() |
VOOZH | about |
This article illustrates using the Vercel ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Vercel 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 Vercel data.
Vercel uses Bearer token authentication. You can use either a personal access token or an OAuth access token as the API key.
To obtain a personal access token:
After obtaining your token, set the following connection properties:
Profile=C:\profiles\Vercel.apip;AuthScheme=APIKey;APIKey=your_access_token;
Many Vercel resources are scoped to a team. To scope all requests to a specific team, set the TeamId connection property to your team's ID. You can find your team ID by querying the Teams table or from the Vercel dashboard. Alternatively, you can specify TeamId in your SQL queries using the WHERE clause where supported.
Once the authentication is configured, you can connect to Vercel and query data from any of the available tables such as Projects, Deployments, Teams, and Domains.
👁 Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT , FROM User 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 Vercel with the API Driver
Connect to Vercel