Many people report that using OPENQUERY() instead of just issuing a "native"
distributed select is faster. I suspect that SQL Server is essentially
getting all of the data from Oracle and then filtering/sorting it locally. I
would think that ODBC would be slower as OLEDB would allow SQL Server to
find out more about what the server can do.

That's not much of an answer, but HTH.

Darin Strait, MS SQL Server Development and Administration
http://home.earthlink.net/~dstrait/professional/resume.htm


----- Original Message -----
From: <john.b.bonifas@b...>
To: "sql language" <sql_language@p...>
Sent: Saturday, June 16, 2001 10:14 PM
Subject: [sql_language] t-sql queries against Oracle linked servers are very
slow


> Hello, All :)  Please excuse me if my questions have already been covered.
>
> When executing transact-SQL queries against an Oracle linked server on our
company's
> shared SQL servers, like this example:
>
> SELECT * from ORACLESERVER..ORACLEOWNER.TABLENAME
>
> they are extremely slow; some queries can take hours. If I place my query
inside a DTS
> package, it often runs much, much faster. Also, I have heard that using
ODBC data sources are
> faster than using OLEDB providers.
>
> My questions are:
>
> What can I do to make my queries against Oracle linked servers run faster?
>
> How can I either modify my queries against linked servers and/or use an
OPENROWSET clause,
> to use the Oracle ODBC driver, instead of the default OLEDB provider?
>
> Thanx in advance to anyone who replies to john.b.bonifas@b...
> (please do not reply to john.b.bonifas@P...),
>
> John B. Bonifas
> Programmer/Analyst - Metrics Unit
> Material Management Organization
> Commercial Airplane Group
> The Boeing Co.
> email: john.b.bonifas@b...
>
>
$subst('Email.Unsub')
>