With a production and a test database on the same server, how should access be provided to some common quarterly update tables for both databases?
It is possible to put these tables into a third database, let us call it catalogs, but then the tables within catalogs can't be accessed as efficiently as if the tables where directly in production or test. On the other hand, space is saved, as there is only one copy of the data.
I see the following two options
- add a user and schema for catalog to both database instances. That gives efficient access, but duplicates space requirements and work to maintain the catalogs
- add a third database instance for catalogs and access this via database links. This saves space, but what about performance.
Which of these solution is better?
Some further information: Catalog has about 60 tables using less than 1GB tablespace. There are functions to be defined in the katalog schema and indexing is important.