In DB2 it’s possible to save temporary tables in the schema SESSION.
SSIS is a product that should be indifferent to whatever RDBMS you use. That’s also true. It will work with every RDBMS through drivers ODBC, OLE DB, ADO.NET etc. BUT it works best with Microsofts SQL-server.
This blogpost will take a look at using IBM DB2 with SSIS. Below is a test using ODBC-driver for IBM DB2 from IBM, OLE DB for IBM DB2 from Microsoft and an ADO.NET-driver.
Transfer rate of data
Transferring 100.000 rows from one IBM DB2-server to another IBM DB2-server.
|OLE DB-driver for IBM DB2 from Microsoft||6 minuts|
|ODBC-driver for IBM DB2 from IBM||5 seconds|
As seen above the ODBC-driver for IBM DB2 from IBM is the best solution when it comes to transfer rate. The OLE DB-driver for IBM DB2 from Microsoft is a really poor choice. But using the ODBC-driver for DB2 from IBM is not the solution to everything!
Lookup-task in SSIS
As seen in the picture below it’s only possible to use an OLE DB-connection in the Lookup-task. The Lookup-task is really slow and it might be better doing it in SQL. Regarding a lot of the tasks in SSIS, they are really slow (see links below).
OLE DB Command
SSIS also contains a ‘OLE DB Command’-task and no ‘ODBC Command’-task.
Fast load/Bulk load
It’s NOT possible to use the fast load option with the OLE DB-driver when it comes to IBM DB2. It’s possible to choose the fastload option, but you will get the error below.
The reason why the OLE DB-driver is that slow is probably that it transfers one row at a time.
It’s possible to use a batch/fast load load option in ODBC.
It’s also possible to use a bulk/fast load option in ADO.NET.
The links below is to different sources that can help you with SSIS.
SQL Server Integration Services Design Patterns
A book that describes different design pattern for SSIS.
Task Factory for SSIS from Pragmatic Works
A collection of optimized SSIS-tasks.
A collection of optimized SSIS-tasks.
PragmaticWorks free online training videos
Free online training videos about SSIS (search for SSIS).
Online training videos in SSIS (requires a paid subscription to Pluralsight).
Select language and the download.
Choose the correct bit-version for you OS.
NB! It has not been possible for me to get this driver to work with SSIS.
The following shows you how I got an ODBC connection to DB2 on a Windows Server 2008R2. After doing a search on the Internet I found this page that really helped me a lot. They do it a bit different.
If you also want to install the IBM Control Center you might want to look at this page. This also installs the ODBC out-of-the-box.
If your need a 32 or 64-bit version for Windows and DB2 version 9.7. You should look for something like this.
On this page you can find and download the ODBC-drivers that fits your system. I you don’t know what version of DB2 that you’re running, you can contact your DBA. The DB2-version can be found using the command DB2level.
Choose either ODBC 32-bit or 64-bit for your DB2-version and download it for Windows.
NB! You need to create an IBM-account to download the file.
Copy the content of ZIP-file containing the ODBC-driver that you just downloaded to c:\program files\IBM. The path is optional, you can choose a different path if you want to or are using a 32-bit ODBC-driver. The files and folders in c:\program files\IBM, should look something like this.
Start a Windows command-prompt as administrator. If you don’t know how to do this, you can take a look at this page.
NB! If you have installed af 32-bit version of the ODBC-driver on a 64-bit system, then you have to look in the 32-bit version of the ODBC Administrator to find the driver. The 32-bit version of the ODBC Administrator can be found here: C:\Windows\SysWOW64\odbcad32.exe (Thanks to Grae for this comment)
Here you need to press the Add-button to add the settings below.
Database: Should point to the database that you want to connect to.
Hostname: Should point to the server where your DB2-server is installed.
Port: The portnumber where the DB2-server on the Hostname is responding.
Protocol: The protocol used to connect to the DB2-server. There’s different options as you can se in the picture below.
The final settings should be the ones listed below.
If you get the error described below in SAS. Then you most likely didn’t install the correct version 32/64-bit for your operating system. Install the correct bit-version of the Control Center from the IBM DB2 Client Server pack (further information at the start of this post).
The SAS/ACCESS Interface to DB2 cannot be loaded. The SASDBU code appendage could not be loaded