|
The optimal performance can only be designed once you know your data access patterns. When you know which tables and indexes are accessed most frequently, you can separate them onto different disk devices so as to not create hot spots for your I/O. You can query V$SEGMENT_STATISTICS (which is not available until Oracle 9i) to see the segments (tables or indexes) with the most physical reads and writes. Prior to 9i, you can set up Statspack and wade through the information there on a file-by-file basis.
But I can give you some overall guidelines. In a SAN, I try to separate my database's files from other database files. This way, an overactive database, from an I/O perspective, does not negatively impact another database. This can also be a good idea from a storage management perspective. If one database grows rapidly, its growth will not constrain growth of the other database.
|
