Making Xtract IS available in Azure-SSIS

Introduction We recently had the chance to test run a private preview version of the Integration Runtime (IR) in Azure Data Factory v2 (ADFv2). With Azure-SSIS, the IR offers SSIS capability through a native compute resource in ADFv2 by providing a managed cluster of Azure VMs (nodes). The idea is to deploy, configure and run your locally developed SSIS packages in the Azure cloud just like you would with SSIS on premises. While Azure-SSIS has been available for public preview since September 2017, running custom SSIS or 3rd party SSIS components currently is…continue reading →

How to use an SQL Configuration Table with Xtract IS

SQL Server Integration Services (SSIS) provides package configurations that you can use to update the values of properties at run time. In this blog I will show how to store your package configuration in an SQL table. In my sample I will use Xtract IS to load the SAP table T001 for company codes using a where statement. The goal is to use the SQL configuration table to update the value of the where statement and the value of the SAP connection string. 785continue reading →

Building SSIS Package with Xtract IS Table Programmatically

In this blog I will show, how to create a SSIS package with Xtract IS Table programmatically. Our Package will extract data from an SAP table and load it to the SQL server. This scenario is very helpful to create your own packages, that you can load and reconfigure for different projects and customers. In this sample we will: create a Package add a data flow task add connection managers add an Xtract IS Table source component add an OLE DB destination component connect data flow components and map columns 316continue reading →

Performing lookups by joining sap data with reference dataset in SSIS

In an SAP table many fields can belong to the table key. In some scenarios when you extract an SAP table with Xtract IS to load it into an SQL table, you want to replace the SAP key fields by another custom key, e.g. a GUID. The customer sales data (KNVV) table e.g. has the following fields as key: MANDT: Client KUNNR: Customer Number VKORG: Sales Organisation VTWEG: Distribution Channel SPART: Division 247continue reading →