Build Data Flows from Sage 200 to SQL Server using SSIS

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 Sage 200 inside of a SQL Server SSIS workflow to transfer Sage 200 data into a Microsoft SQL Server database.

Add the Components

To get started, add a new Sage 200 source and SQL Server ADO.NET destination to a new data flow task.

Create a New Connection Manager

Follow the steps below to save Sage 200 connection properties in a connection manager.

1. In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
2. In the Connection Manager type menu, select Sage200. The CData Sage 200 Connection Manager is displayed.
3. Configure connection properties.
   • Schema: Determines which Sage 200 edition you are connecting to. Specify either StandardUK or ProfessionalUK.
   • Subscription Key: Provides access to the APIs that are used to establish a connection. You will first need to log into the Sage 200 API website and subscribe to the API edition that matches your account. You can do so here: https://developer.columbus.sage.com/docs/services/api/uk. Afterwards, the subscription key may be found in your profile after logging into Sage 200.
   👁 Configuring a connection (Salesforce is shown).
   

Configure the Sage 200 Source

Follow the steps below to specify the query to be used to extract Sage 200 data.

1. Double-click the Sage 200 source to open the source component editor.
2. In the Connection Manager menu, select the connection manager previously created.
3. Specify the query to use for the data extraction. For example:

   SELECT Id, Code FROM Banks WHERE Code = '12345'
   

   👁 The SQL query to retrieve records. (Salesforce is shown.)
   
4. Close the Sage 200 Source control and connect it to the ADO.NET Destination.

Configure the SQL Server Destination

Follow the steps below to specify the SQL server table to load the Sage 200 data into.

1. Open the ADO.NET Destination and add a New Connection. Enter your server and database information here.
2. In the Data access mode menu, select "table or view".
3. In the Table Or View menu, select the table or view to populate.
4. Configure any properties you wish to on the Mappings screen. 👁 The mappings from the SSIS source component to SQL Server. (Salesforce is shown.)
   

Run the Project

You can now run the project. After the SSIS Task has finished executing, your database will be populated with Sage 200 data.