I am using IBMDA400 driver in SQL integration services.I do not want to turn on Journaling on the tables I am writing to. I need to figure out a way to turn off Commitment control with using the IBMDA400 driver properties. Can anybody help with me with this?

Does anybody know how to get rid of the commitment control of the AS400 when using it as a destination with the IBMDA400 OLEDB driver?? We don't want to set journalling on but we want to write data to this server with SSIS. Thanks!

I'm not sure this is an SSIS question. Have you posted to an IBM support forum? If you can set a switch in a connection string, then you can do so in SSIS...

Actually the problem is that we use SSIS and we have to store data in an IBM AS400 database. I read so many articles and forums about the combination of SSIS and IBM AS400 as a destination but nothing helped. The following is working: We use the IBMDASQL OLEDB driver of iSeries (IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider) (and forget about journaling) and use the OLE DB Destination but this is very very slow and not workable. So we tried an other driver of the iSeries (IBMDA400) but then we got the journaling issues. And even when we turn on journaling it is as slow as the previous solution. We wanted to try to write data via ODBC but after reading al forums we skipped that. We even downloaded the Microsoft OLE DB provider for DB2 but that doesnt make any sense since weve got the Standard Edition of SQL Server 2005. So I hope somebody had got good experience with SSIS in combination with DB2 as a destination? What kind of driver should we use and are there any special driver settings we have to set?

Again, this is likely the IBM driver causing your issues. Here's what you can try... For $50 (if you don't have it already), you can download and install the developer edition of SQL Server. This is the same as Enterprise, except for non-production use. You can use this to determine if the Microsoft OLE DB for DB2 driver works better. As always, I'll tell you to try writing to DB2 using the IBM driver using another tool other thanSSIS and see if the performance is any different.

Were you ever able to determine if Microsoft OLE DB for DB Provider had any perforance increase as compared to the IBMDBASQL OLE DB provider?

One solution is, once you have conntected to the AS/400 (iSeries, i) execute this command just as you would any SQL statement: SET OPTION COMMIT=*NONE ;