Ready to get started?

Learn more about the CData SSIS Components for Sage 200 or download a free trial:

Download Now

Export Data from SQL Server to Sage 200 through SSIS

Easily push SQL Server data to Sage 200 using the CData SSIS Tasks for Sage 200.

SQL Server databases are commonly used to store enterprise records. It is often necessary to move this data to other locations. The CData SSIS Task for Sage 200 allows you to easily transfer Sage 200 data. In this article you will export data from SQL Server to Sage 200.

Add Source and Destination Components

To get started, add a new ADO.NET Source control and a new Sage 200 Destination control to the data flow task.

Configure the ADO.NET Source

Follow the steps below to specify properties required to connect to the SQL Server instance.

  1. Open the ADO.NET Source and add a new connection. Enter your server and database information here.
  2. In the Data access mode menu, select "Table or view" and select the table or view to export into Sage 200.
  3. Close the ADO NET Source wizard and connect it to the destination component.

Create a New Connection Manager for Sage 200

Follow the steps below to set required connection properties in the Connection Manager.

  1. Create a new connection manager: In the Connection Manager window, right-click and then click New Connection. The Add SSIS Connection Manager dialog is displayed.
  2. Select CData Sage200 Connection Manager in the menu.
  3. Configure the 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.

Configure the Sage 200 Destination

In the destination component Connection Manager, define mappings from the SQL Server source table into the Sage 200 destination table and the action you want to perform on the Sage 200 data. In this article, you will insert Banks entities to Sage 200.

  1. Double-click the Sage 200 destination to open the destination component editor.
  2. In the Connection Managers tab, select the connection manager previously created.
  3. In the Use a Table, menu, select Banks. In the Action menu, select Insert.
  4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns.

Run the Project

You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.