![]() |
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 ScrapingBee inside of a SQL Server SSIS workflow to transfer ScrapingBee data into a Microsoft SQL Server database.
To get started, add a new ScrapingBee 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 ScrapingBee connection properties in a connection manager.
ScrapingBee uses API key authentication. To obtain an API key:
After obtaining your API key, set the following connection properties:
Profile=C:\profiles\ScrapingBee.apip;AuthScheme=APIKey;ProfileSettings="APIKey=your_api_key";
Once the authentication is configured, you can connect to ScrapingBee and query data from any of the available tables. All tables require at least one input parameter (such as a search query or product ID) to retrieve data.
๐ Configuring a connection (Salesforce is shown).Follow the steps below to specify the query to be used to extract ScrapingBee data.
SELECT , FROM GoogleSearchResults WHERE SearchQuery = 'cdata drivers'๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the ScrapingBee data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with ScrapingBee data.
๐ The completed import. (Salesforce is shown.)Connect to live data from ScrapingBee with the API Driver
Connect to ScrapingBee