Re: Database links

The main point of the question ( not whether they should be divided ) is whether the database link will cause any performance bottleneck

--
Cheers

Steve Bright

steve.bright_at_capgemini.co.uk

tedchyn_at_yahoo.com wrote in message <7iehok$1me$1_at_nnrp1.deja.com>...
>steve, To divide or not to divide is depending on size of database,
>number of users and usage pattern of your database.
>Ted
>In article <7iebqo$or6$1_at_taliesin.netcom.net.uk>,
> "Super Kev" <steve.bright_at_capgemini.co.uk> wrote:
>> At present we have two instances on the same server, with a database
>link
>> between the two. The two instances are fairly independant of each
>other but
>> require some interaction. One is accessed via the Oracle Application
>Server,
>> the other mainly accessed by a VB client / server set up.
>>
>> Basically I am wondering whether it is better to have only one
>instance, and
>> separating the schemas, or to keep the current two instances setup. My
>> instinct tells me to keep them seperate, mainly for backup, recovery,
>> maintenence purposes.
>>
>> However, will the database link cause any bottlenecks ???
>>
>> Does anyone have any experience of this ????
>>
>> --
>> Cheers
>>
>> Steve Bright
>>
>> steve.bright_at_capgemini.co.uk
>>
>>
>
>
>--== Sent via Deja.com http://www.deja.com/ ==--
>---Share what you know. Learn what you don't.---
Received on Wed May 26 1999 - 03:49:04 CDT