I have 2 boxes running SQL Server 2008 and using linked Oracle OLEDB that behaves different for same query.
On 1st machine, using win 2003 , SQL Server 2008 SP1 on a 64-bit server I I created a linked server to Oracle database using Oracle OLEDB provider. When I submit query to a Oracle database using Oracle OLEBD using WHERE clause, this WHERE clause
is sent to Oracle, then it uses an index to resolve query and send result already filttered to SQL Server.
I have a 2nd box running Windows 2008 R2, SQL 2008 SP2 on a 64-bit server and queries are working fine, but when I filter some column of a linked server table using WHERE clause, SQL Server sends to Oracle SELECT without where clause, Oracle performs a table
scan on that table and then sends results to SQL Server, that applies filter to the result.
The problem is that some Oracle tables are huge and sending a SELECT without where clause causes table scans on Oracle, what should be avoided.
I already tried to change OLEDB properties and also tried to change linked server properties, but none of them solved the problem.
Does anyone knows what I should change on 2nd server to make it works like 1st server?
Se a resposta resolveu sua questÃÂ£o ou problema, classifique-a para manter a qualidade do forum e a confiabilidade dos p
View Complete Post