We have several large "look-up" tables that we use in development as well as in
production environments. The data is the same in both environments. I am
looking for some comments regarding whether or not we store duplicate data in
each environment or should we allow the development users to access the table
in production through a database link. Below, I have listed some issues with
both of these processes and am looking for further input. Thanks
Duplicate table in production and development (either through export/import or
snapshots):
Cons
additional storage is need
process needed to keep tables in sync
Pros
reduced network traffic
Access table in production through a database link in development:
Cons
additional network traffic
possibility of poorly tuned adhoc sql executing in a production
environment
Pros
only one copy of table
do not need an ongoing process to keep the tables in sync
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Tracy Rahmlow
INET: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] (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).
