I'm executing SQL statements through the Client Access ODBC driver against an iSeries V4R2M0. It works, but the time response is very high --around two to three minutes. This is unacceptable for my application. Is there another way to issue SQL statements to the DB2/400, or is there another ODBC driver better than the Client Access driver? Remember, the SQL statement is just a SELECT.
Slow performance is almost always not an ODBC driver issue but an SQL issue. That is the SQL you requested will probably run as bad on iSeries local session.
Why? It is possible that the request is selecting rows based on non-indexed selection columns, it is also possible that it must create an index to perform join.You need to troubleshoot the SQL performance.
Click here for an example.
MORE INFORMATION ON THIS TOPIC
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: Tips, tutorials and more.
Dig Deeper on iSeries Access (Client Access)
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.