![]() |
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 Perplexity inside of a SQL Server SSIS workflow to transfer Perplexity data into a Microsoft SQL Server database.
To get started, add a new Perplexity 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 Perplexity connection properties in a connection manager.
Start by setting the Profile connection property to the location of the Perplexity Profile on disk (e.g. C:\profiles\Perplexity.apip). Next, set the ProfileSettings connection property to the connection string for Perplexity (see below).
Visit the Perplexity API dashboard at https://www.perplexity.ai/settings/api to generate an API key.
๐ Configuring a connection (Salesforce is shown).Follow the steps below to specify the query to be used to extract Perplexity data.
SELECT RequestId, Model FROM AsyncJobResults WHERE Status = 'COMPLETED'๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the Perplexity data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Perplexity data.
๐ The completed import. (Salesforce is shown.)Connect to live data from Perplexity with the API Driver
Connect to Perplexity