Export Data from SQL Server to EnterpriseDB through SSIS

Ready to get started?

Download for a free trial:

Download Now

Learn more:

EnterpriseDB SSIS Components

Powerful SSIS Source & Destination Components that allows you to easily connect SQL Server with EnterpriseDB through SSIS Workflows.

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



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

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 EnterpriseDB allows you to easily transfer EnterpriseDB data. In this article you will export data from SQL Server to EnterpriseDB.

Add Source and Destination Components

To get started, add a new ADO.NET Source control and a new EnterpriseDB 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 EnterpriseDB.
  3. Close the ADO NET Source wizard and connect it to the destination component.

Create a New Connection Manager for EnterpriseDB

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 EnterpriseDB Connection Manager in the menu.
  3. Configure the connection properties.

    The following connection properties are required in order to connect to data.

    • Server: The host name or IP of the server hosting the EnterpriseDB database.
    • Port: The port of the server hosting the EnterpriseDB database.

    You can also optionally set the following:

    • Database: The default database to connect to when connecting to the EnterpriseDB Server. If this is not set, the user's default database will be used.

    Connect Using Standard Authentication

    To authenticate using standard authentication, set the following:

    • User: The user which will be used to authenticate with the EnterpriseDB server.
    • Password: The password which will be used to authenticate with the EnterpriseDB server.

    Connect Using SSL Authentication

    You can leverage SSL authentication to connect to EnterpriseDB data via a secure session. Configure the following connection properties to connect to data:

    • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
    • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSLClientCertType: The certificate type of the client store.
    • SSLServerCert: The certificate to be accepted from the server.

Configure the EnterpriseDB Destination

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

  1. Double-click the EnterpriseDB 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 Orders. 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.