![]() |
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 Placid inside of a SQL Server SSIS workflow to transfer Placid data into a Microsoft SQL Server database.
To get started, add a new Placid 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 Placid connection properties in a connection manager.
Placid uses API Key authentication to control access to the API. API tokens are project-specific and can be obtained from your project settings on placid.app.
To obtain your API key, log in to placid.app, navigate to your project, open the project settings, and generate an API token from the API section. Note that each API token is scoped to a specific project.
After setting the following connection properties, you are ready to connect:
Profile=C:\profiles\Placid.apip;AuthScheme=APIKey;ProfileSettings='APIKey=your_project_api_token';๐ Configuring a connection (Salesforce is shown).
Follow the steps below to specify the query to be used to extract Placid data.
SELECT , FROM Collections WHERE = ''๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the Placid data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Placid data.
๐ The completed import. (Salesforce is shown.)Connect to live data from Placid with the API Driver
Connect to Placid