×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Using the JTOpen JDBC driver, the SQuirreL client does not suffer from this issue.
-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxx]
Sent: Thursday, July 09, 2015 12:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: Speeding up ODBC
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.
The statement inside openquery() has to be in the syntax of the remote server - no problem for you, seems you're handling both sides.
I realize I might be repeating some of what was said in that other recent thread - but this is good stuff to know and understand. And not something we'd expect.
Thing is, these clients assume least-common-denominator on this stuff - and with ODBC you can use a "standard" syntax for everyone.
Anyone know, is there a similar issue with JDBC?
Vern
On 7/9/2015 12:04 PM, rob@xxxxxxxxx wrote:
That made an amazing difference. It changed a query against a +1m row
table from "never completing" into subsecond response.
Rob Berendt
midrange.com
