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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tablespace Recommendations

Status
Not open for further replies.

dbomrrsm

Programmer
Feb 20, 2004
1,709
GB
I have recently read that in a reporting system where two tables are frequently joined together as part of queries they should be stored within seperate tablespaces.

This was in a document under a section entitled:

Tablespace Recommendations

Can anyone throw any light on why this sould be done ?

TIA

[bandito] [blue]DBomrrsm[/blue] [bandito]

[blue]Software code, like laws and sausages, should never be examined in production[/blue][black] - [/black][purple]Edward Tenner[/purple]
 
The reason would be to reduce disk contention. If the two tables are both on the same disk and queries are always having to access both of them, that is doubling the amount of I/O on that disk. It therefore makes sense to have them on different devices. With newer technologies like disk striping, a lot of this sort of advice is redundant.
 
Dagon

Thanks for the explanation.


[bandito] [blue]DBomrrsm[/blue] [bandito]

[blue]Software code, like laws and sausages, should never be examined in production[/blue][black] - [/black][purple]Edward Tenner[/purple]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top