RE: DB Links

  • From: "Gogala, Mladen" <Mladen.Gogala@xxxxxxxx>
  • To: "'Goulet, Dick'" <DGoulet@xxxxxxxx>, thomas.mercadante@xxxxxxxxxxxxxxxxx, adar76@xxxxxxxxxxxx, "adar76@xxxxxxxxxxxx" <adar76@xxxxxxxxxxxx>, "Oracle-L (E-mail)" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 23 Sep 2004 10:57:07 -0400

This depends on the version of the database on the driving site.
If your driving site runs 8i, ALL of the data will be brought back
and filtered locally. In 9i, the behavior is that single table 
access predicates that can be resolved remotely, are resolved 
remotely. Oracle 10g uses gridlock method for remote execution.
Just kidding, haven't actually tried with 10.

Mladen Gogala
A & E TV Network
Ext. 1216

> -----Original Message-----
> From: Goulet, Dick [mailto:DGoulet@xxxxxxxx] 
> Sent: Thursday, September 23, 2004 10:53 AM
> To: Mladen.Gogala@xxxxxxxx; 
> thomas.mercadante@xxxxxxxxxxxxxxxxx; adar76@xxxxxxxxxxxx; 
> adar76@xxxxxxxxxxxx; Oracle-L (E-mail)
> Subject: RE: DB Links
> Mladen,
>       My experience is somewhat different from yours.  In the 
> case of "FROM EMP@LINK WHERE EMPNO = 1234" I have found that 
> the local database will pass that along to the remote 
> database for resolution since there will definelty be one and 
> only one row returned.  Now "FROM EMP@LINK WHERE EMPNO > 
> 1234" would also resolve itself on the remote db, but "FROM 
> dept a, EMP@LINK b WHERE a.empno = b.empno and b.EMPNO > 
> 1234" will result in emp becoming a local temp table.

Other related posts: