Hi,

You said:

"we have 30 schools each with their own instance. "

If they all use schema with similar table structures, could you consider
merging the tables using VPD? Then you could segregate the data and
reduce the number of instances/schemas to manage considerably!

Lloyd


-----Original Message-----
From: Dawn Syverson
[mailto:oracledba-ezmlmshield-x51571283.[Email address protected]
Sent: 28 July 2005 16:43
To: LazyDBA Discussion
Subject: RE: where to begin

Thank you this is great. FYI: all instances are used for reporting and
ad hoc queries - we have 30 schools each with their own instance. None
are testing or development and none can be eliminated.

The path I would follow are :

1) Eliminate instances you do not need or perhaps you may be able to
combine use of instances?

2) From the list of remaining instances, take out those used as
development, uat, performace etc.. These non-production instances
should be housed in a separate server/domain.

Now you essentially have 2 main options.

1) Have one large machine capable of running all these instances..( ie.
SUnE15K for example ) . Have one database instance and use different
schemas for separation. However, you will need to segregate machine and
I/O resource by use of Resource Manager.

2) Go for Oracle RAC, and one database instance. Still use separate
schema to achieve the 'data' separation you may require. However, the
server resources are now handled via the RAC nodes.


3) use of row level security, streams etc , I would suggest, are not
ideal for the type of consolidation you want.

I've been through the same exercise and hence my suggestions.

Harish.




--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page