![]() |
VOOZH | about |
Using SQL Server as a backup for critical business data provides an essential safety net against loss. Backing up data to SQL Server enables business users to more easily connect that data with features like reporting, analytics, and more.
This example demonstrates how to use the CData SSIS Tasks for Vercel inside of a SQL Server SSIS workflow to transfer Vercel data into a Microsoft SQL Server database.
To get started, add a new Vercel source and SQL Server ADO.NET destination to a new data flow task.
๐ The Data Flow task used in this example. (Salesforce is shown.)Follow the steps below to save Vercel connection properties in a connection manager.
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.
๐ Configuring a connection (Salesforce is shown).Follow the steps below to specify the query to be used to extract Vercel data.
SELECT , FROM User WHERE = ''๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the Vercel data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Vercel data.
๐ The completed import. (Salesforce is shown.)Connect to live data from Vercel with the API Driver
Connect to Vercel