dbTalk Databases Forums  

purpose of db-links

comp.database.oracle comp.database.oracle


Discuss purpose of db-links in the comp.database.oracle forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
bdj
 
Posts: n/a

Default purpose of db-links - 07-26-2005 , 12:06 PM






Hi!
I have seen db-links used in views, triggers etc.
This results in very bad performance.
Is there an good reference to read about, when and when not to use db-links?
Greetings
Bjørn



Reply With Quote
  #2  
Old   
Mark Malakanov
 
Posts: n/a

Default Re: purpose of db-links - 08-01-2005 , 09:44 AM






Depends why do you use them. You usually use them when you have to
get/put data from/into another DB.
You can avoid to use DB links directly from triggers and other code by
separating of local DML code and a propagation of data modifications -
Replication. There are two major facilities that can help with that.
Standard Replication and Adwanced Replication. Although they will use DB
Links too (inside), your app will work with a local replica of remote
data, that is much faster. Replication will move data or data changes
here and there. It is called asynchronous replication.
However the asynchronous replication from remote to local will cause
some de-synchronization in data between them. The latency of data
modifications coming. That is the price. The latency depends on what
type of replication you use and settings.
It is achievable to have asynchronous replication based on Streams (10g)
that can be close to real time.
If totally momentarily data is required to be accessed, you can not
avoid using db links.



bdj wrote:
Quote:
Hi!
I have seen db-links used in views, triggers etc.
This results in very bad performance.
Is there an good reference to read about, when and when not to use db-links?
Greetings
Bjørn



Reply With Quote
  #3  
Old   
bdj
 
Posts: n/a

Default Re: purpose of db-links - 08-01-2005 , 03:49 PM



Thank you!!


"Mark Malakanov" <markmal (AT) rogers (DOT) com> skrev i en meddelelse
news:JMCdnR5XmvywqHPfRVn-sA (AT) rogers (DOT) com...
Quote:
Depends why do you use them. You usually use them when you have to get/put
data from/into another DB.
You can avoid to use DB links directly from triggers and other code by
separating of local DML code and a propagation of data modifications -
Replication. There are two major facilities that can help with that.
Standard Replication and Adwanced Replication. Although they will use DB
Links too (inside), your app will work with a local replica of remote
data, that is much faster. Replication will move data or data changes here
and there. It is called asynchronous replication.
However the asynchronous replication from remote to local will cause some
de-synchronization in data between them. The latency of data modifications
coming. That is the price. The latency depends on what type of replication
you use and settings.
It is achievable to have asynchronous replication based on Streams (10g)
that can be close to real time.
If totally momentarily data is required to be accessed, you can not avoid
using db links.



bdj wrote:
Hi!
I have seen db-links used in views, triggers etc.
This results in very bad performance.
Is there an good reference to read about, when and when not to use
db-links?
Greetings
Bjørn



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.