Import Epicor Kinetic Data into SQL Server using SSIS

Ready to get started?

Download a free trial of the Epicor Kinetic SSIS Component to get started:

 Download Now

Learn more:

Epicor Kinetic Icon Epicor Kinetic SSIS Components

Powerful SSIS Source & Destination Components that allows you to easily connect SQL Server with live Epicor Kinetic data through SSIS Workflows.

Use the Epicor Kinetic Data Flow Components to synchronize with Epicor Kinetic constructs. Perfect for data synchronization, local back-ups, workflow automation, and more!

Easily back up Epicor Kinetic data to SQL Server using the SSIS components for Epicor Kinetic.

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

Add the Components

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

Create a New Connection Manager

Follow the steps below to save Epicor Kinetic 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 epicorKinetic. The CData Epicor Kinetic Connection Manager is displayed.
  3. Configure connection properties.

    To successfully connect to your ERP instance, you must specify the following connection properties:

    • Url:the URL of the server hosting your ERP instance. For example,
    • ERPInstance: the name of your ERP instance.
    • User: the username of your account.
    • Password: the password of your account.
    • Service: the service you want to retrieve data from. For example, BaqSvc.

    In addition, you may also set the optional connection properties:

    • ApiKey: An optional key that may be required for connection to some services depending on your account configuration.
    • ApiVersion: Defaults to v1. May be set to v2 to use the newer Epicor API.
    • Company: Required if you set the ApiVersion to v2.

Configure the Epicor Kinetic Source

Follow the steps below to specify the query to be used to extract Epicor Kinetic data.

  1. Double-click the Epicor Kinetic 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 CustNum, Company FROM Customers WHERE CompanyName = 'CompanyName'
  4. Close the Epicor Kinetic 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 Epicor Kinetic 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.

Run the Project

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