Clever Geek Handbook

ODBC AS / 400 Drivers

We used the ODBC Client Access driver when accessing AS / 400 data from our .net applications and SQL DTS / SSIS packages. Are there third party drivers that provide better performance or functionality?

0


source to share


5 answers


Our company uses the same client access drivers. As far as we know, there are no others. One of the problems we ran into last year was that there were no 64-bit drivers, so our servers that have applications connecting to the AS / 400 must be 32-bit.



+2


source


I know this is on the other side of the hill, but I used JTOpen as JDBC (well, Java ...) in a previous project. This is the Java version of the OpenSource IBM Toolbox . Typically some pre-release version of IBM and fewer bugs. My experience with this driver has been very positive.



+1


source


You can use the built-in Windows drivers to connect, but I think the IBM driver will be faster.

Are you seeing a performance hit or are you just trying to squeeze out more performance? If it is the first, take a look at your system to see if it has executed correctly. At the old job, the system was too small for what we use it for. Some simple queries took a few minutes. If it's the latter, maybe try adding some more RAM to the i.

+1


source


I'm not sure if this is better, but a quick google shows up Hit ODBC / 400 .

0


source


IBM is consolidating its DB2 drivers, so the generic DB2 driver must be able to connect to DB2 / 400.

I haven't tried it yet. I would like to hear your impressions.

0


source






More articles:


All Articles