Basic principles of oracle Tablespace Design

This article mainly explains the "basic principles of oracle tablespace design". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn the basic principles of oracle tablespace design.

In order to facilitate our dba's daily management of oracle database, combined with our daily work and some suggestions in books, we summarize the following suggestions here:

1. System data and application data must be stored in different table spaces.

2. Divide the data according to the application, and the data of different applications should be stored in different table spaces.

3. Tables and indexes are separated and need to be stored in different table spaces so that they can be distributed to different data files and hard disks, and different physical storage parameters are optimized respectively.

4. Relatively static tables and frequently changing tables are stored separately in different table spaces in order to optimize different physical parameters.

5. Design a separate tablespace for the intermediate table, without considering backup.

6. Temporary tablespace group technology is adopted to improve the efficiency of mass data processing.

Thank you for your reading, the above is the content of "the basic principles of oracle tablespace design". After the study of this article, I believe you have a deeper understanding of the basic principles of oracle tablespace design, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!