Build Data Flows from SQL Server to AlloyDB through SSIS

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

Add Source and Destination Components

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

Create a New Connection Manager for AlloyDB

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

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

   No further action is required to leverage Standard Authentication to connect.

   Authenticating with pg_hba.conf Auth Schemes

   There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

   Find instructions about authentication setup on the AlloyDB Server here.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

Configure the AlloyDB Destination

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

1. Double-click the AlloyDB 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. 👁 The destination table and action to be performed.
   
4. On the Column Mappings tab, configure the mappings from the input columns to the destination columns. 👁 The mappings from the SQL Server source to the SSIS destination component.
   

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.