I've got a package that imports data from informix database. I'm using iBM Informix ODBC Driver 3.50 with ADO.NET data source to import data. Every now and then the package fails with "Could not do physical order read to fetch next row" issue so
did some investigation and found that its due to the lock issue. Most of the guys suggested setting up isolation level to "Dirty Read".
Is it the only option to import data consistenly without any error from Informix? Because with "Dirty Read" you get concurrency issue.
My other question is; can we use the transaction option with isolation level available is SSIS to get around this issue and if yes then how to approach it. And if it's no then is it limited to oledb sources only.
View Complete Post