Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Arguably, for very frequently used and cached tables you might put them on the slower disks. In any case I'd be sure to look at v$_segment_stats for physical i/o when deciding which to place where.
–
David AldridgeJun 13 '13 at 10:27

1 Answer
1

You can create two tablespaces, put all the data files for one tablespace on one drive and all the data files for the other tablespace on the other side, and then create the tables in whichever tablespace you would like. It seems unlikely, however, that you would really want to do this. It is very unusual to run a database on a server without any sort of RAID configuration. And it is generally the case that any automatic I/O load balancing that you would implement would outperform your manual load balancing.

-1 for the last comment. While I am all to have the system do the work, it is not THAT Unusual to have DAS (Directly Atached Storage) and separate core high throughput and lower throughput for example for archive tables. I Know of some databases (one here in my work) deploying three levels actually - because some tables see a TON of activity, others do not, especially in the update area. A Raid controller will not magically make a decent decision - especially not taking financials into account.
–
TomTomJun 13 '13 at 8:19

3

@TomTom - I did say "generally". There are certainly systems that deal with a lot of historical data where having storage tiers makes sense. Though those systems would still have a separate RAID array for each storage tier rather than using a single drive. It is still generally the case that it would be very difficult for most systems to figure out how to manually distribute objects to maximize performance in this sort of setup unless you're willing to spend ridiculous amounts of time monitoring and redistributing load.
–
Justin CaveJun 13 '13 at 9:18