Splitting a database: pro and cons

From: Djordje Jankovic <djankovic_at_corp.attcanada.ca>
Date: Tue, 14 Aug 2001 14:45:55 -0700
Message-ID: <F001.0036AA09.20010814145145@fatcity.com>

Hi list,

I have two applications running against one database (in fact I have a few but for the sake of this question two are enough). The two apps have different upgrade patterns and I would like to split them in two databases that will be on the same unix server. There are some views that are used extensively that join data from both apps/schemas, and after the split those should be made using db links. I did some tests and comparisons of queries going through links versus running them directly on the database, and did not see a lot of difference.

Does anybody see or know of any downside in splitting the database in two :-(. And any advantage :-). What is the general strategy when installing different apps (from different vendors) - put them on separate databases or combining them.

Thanks.

Djordje
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Djordje Jankovic
  INET: djankovic_at_corp.attcanada.ca

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Aug 14 2001 - 16:45:55 CDT