![]() |
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 Procore inside of a SQL Server SSIS workflow to transfer Procore data into a Microsoft SQL Server database.
To get started, add a new Procore 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 Procore connection properties in a connection manager.
Start by setting the Profile connection property to the location of the Procore Profile on disk (e.g. C:\profiles\Procore.apip). Next, set the ProfileSettings connection property to the connection string for Procore (see below).
To authenticate to Procore, and connect to your own data or to allow other users to connect to their data, you can use the OAuth standard.
First, register an OAuth application with Procore. You can do so by logging to your Developer Account and going to Create New App. Follow all necessary steps to register your app. First create a new version of Sandbox Manifest and then promote it to Production in order to get your Production Crendentials. Your Oauth application will be assigned a client id and a client secret.
After setting the following connection properties, you are ready to connect:
Follow the steps below to specify the query to be used to extract Procore data.
SELECT Id, Name FROM Companies WHERE IsActive = 'true'๐ The SQL query to retrieve records. (Salesforce is shown.)
Follow the steps below to specify the SQL server table to load the Procore data into.
You can now run the project. After the SSIS Task has finished executing, your database will be populated with Procore data.
๐ The completed import. (Salesforce is shown.)Connect to live data from Procore with the API Driver
Connect to Procore