Hello, We have two schemas with different tables. Some of the tables have same structure and share same data. Could you suggest if I should use synonyms (keeping the shared tables in one of those schemas only) or a new schema for them? Is combining the databases any good?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
shared tables 2
- Thread starter DBrack
- Start date
-
1
- #2
SantaMufasa
Technical User
D,
Your question is similar to "Is it better to rent, lease, or own a vehicle". The answer is, obviously, "It depends."
Typically, I have found great advantage to have a single schema own the objects (tables, indexes, et cetera) for a particular application, then extend appropriate privileges to other schemae/users.
But, certainly, there are many cases where the objects necessary to do business reside in multiple schemae. Under such circumstances, I use PUBLIC SYNONYMS to reduce the implication of schema qualification.
I hope some of these thoughts are useful to you. Please let us know.
![[santa]](/data/assets/smilies/santa.gif "[santa] [santa]")
Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
Your question is similar to "Is it better to rent, lease, or own a vehicle". The answer is, obviously, "It depends."
Typically, I have found great advantage to have a single schema own the objects (tables, indexes, et cetera) for a particular application, then extend appropriate privileges to other schemae/users.
But, certainly, there are many cases where the objects necessary to do business reside in multiple schemae. Under such circumstances, I use PUBLIC SYNONYMS to reduce the implication of schema qualification.
I hope some of these thoughts are useful to you. Please let us know.
Mufasa(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
-
1
- #3
I would merge the schema's
The reason for doing this is to simplify the administration and to do away with two applications using common tables with others split. This is a recipe for a migration nightmare.
Do the programs do associated business functions if so merge the applications as well.
I have a set of applications where I am and it was decided to split applications across multiple servers, It was found after the split that in fact there was dependency , we are now cleaning that up. common stuff in separate applications that properly hadnt been shared
Technology Consultant, Australia
"So much of what we call management consists of making it difficult for
people to work" --- Peter Drucker
The reason for doing this is to simplify the administration and to do away with two applications using common tables with others split. This is a recipe for a migration nightmare.
Do the programs do associated business functions if so merge the applications as well.
I have a set of applications where I am and it was decided to split applications across multiple servers, It was found after the split that in fact there was dependency , we are now cleaning that up. common stuff in separate applications that properly hadnt been shared
Technology Consultant, Australia
"So much of what we call management consists of making it difficult for
people to work" --- Peter Drucker
- Status
Similar threads
- Locked
- Question