Home » RDBMS Server » Server Administration » Schema Creation
Schema Creation [message #130466] Sun, 31 July 2005 01:02 Go to next message
sarfraz_attari
Messages: 123
Registered: July 2005
Senior Member
write now we have 4 seperate schemas in our database now we are going to transfer all the tables in single schema
is it a good practice

pl suggest

sarfraz
Re: Schema Creation [message #130469 is a reply to message #130466] Sun, 31 July 2005 01:19 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
depends on what you do.
If all the four schemas are of different applications, have them in different schemas
Performance wise it makes no difference

[Updated on: Sun, 31 July 2005 01:19]

Report message to a moderator

Re: Schema Creation [message #130470 is a reply to message #130469] Sun, 31 July 2005 01:52 Go to previous messageGo to next message
sarfraz_attari
Messages: 123
Registered: July 2005
Senior Member
thanks for ur reply
yes these four schema is of seperate application
but performance wise if there is no problem then we can keep it in single schema
Re: Schema Creation [message #130489 is a reply to message #130470] Sun, 31 July 2005 09:13 Go to previous messageGo to next message
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
Senior Member
Account Moderator
that means, all the applications reside the same set of tablespaces.
If that tablespace/datafile corrupts, all application is in trouble.
having in different schema and dedicated tablesapce for each schema is ease for administration.
You can individually backup / restore tablespcae, export/import etc.
Re: Schema Creation [message #130603 is a reply to message #130466] Mon, 01 August 2005 07:26 Go to previous message
smartin
Messages: 1803
Registered: March 2005
Location: Jacksonville, Florida
Senior Member
In general, I like as few schemas as reasonable. But at the same time, if there are truly separate applications, who don't access each others data regularly as part of their application work, then I'd keep them as separate schemas (I actually like 2 per app, one for data and one for code that operates on that data).

But in your case, you already have separate schemas, so my question would be why are you considering a change in the first place?
Previous Topic: Dropped Table is not available in Recyclebin
Next Topic: Duplication of oracle database.
Goto Forum:
  


Current Time: Thu Sep 26 22:48:42 CDT 2024