Re: Speeding up ODBC

On 09-Jul-2015 11:21 -0600, Mike Cunningham wrote:

On Thursday, July 09, 2015 1:16 PM Vernon Hamberg wrote:

Yup - in talking with one of our SQL Server folks, he said that
things like SQL Server will take a statement like that and
basically do a SELECT * FROM TABLE on the remote server - no WHERE
clause is passed along.

Then they do the filtering on the client. Crystal Reports was/is
like that, too - one was encouraged in CR to turn on a setting to
force the whole query to run on the remote server.

The behavior of running SELECT * with no selectivity is a
well-known one, according to Rick, the guy I talked to.
<<SNIP>>

Does anyone have any experience with the IBM ODBC Driver for Linux
and it might also behave like this and ignore the where clause?

The client software would be dropping the WHERE criteria, not the driver.

We don't have an issue with speed with incoming ODBC requests from
this linux application but they do have a big CPU hit when they run.
Up to 40-50% when running. And building indexes to try and help has
not.

Maximizing CPU utilization is often a good thing, except if the utilization impacts other work that is prioritized. Optimize for efficiency; for sure do *not* optimize to minimize CPU utilization.