Oracle database, the design table, under what circumstances need to build the table partitioning? Have a standard? What's good about than building partition?

CodePudding user response:

The building Lord first to know about the basic knowledge of the partition table, and features,

Baidu and the website can be,

CodePudding user response:

You can go online to understand under
1. What is the partition table?
2. What are the types of the partition table?
3. In what situations?
4. The role of the partition table
,,,,,,
You will naturally understand,

The partition table is the most important two benefits:
1. Easy to maintain and manage data,
2. Improve query performance,

CodePudding user response:

If only consider applications, simple and crude to say: the index of partition is large, when your index cannot respond to queries is the partition
If you still consider operations, management, should consider the most is history data how to deal with this problem

CodePudding user response:

reference minsic78 reply: 3/f

if only consider applications, simple and crude to say: partition index is large, when your index cannot respond to queries is the partition
If you still consider operations, management, should consider the most is historical data, how to deal with the problem

Integrated both, or choose to

CodePudding user response:

Understanding of oracle partition table to sort out
http://blog.itpub.net/30130773/viewspace-2121413/

This article should be helpful to you,

CodePudding user response:

Table partitioning of the advantages of few said, 1, improve query performance; 2, and enhance availability; 3, maintenance is convenient; 4, balance the I/O;
Amount of data is very large, and often carried out in accordance with the a field filter or as a group, can consider to use partition

CodePudding user response:

When the table size reaches GB level and continues to grow, or for OLTP systems, table records of more than 10 million, should consider to partition table,

Oracle's two Suggestions as follows:
Tables greater than 2 gb should always be considered for partitioning.
Tables containing historical data, in which new data is added into the newest partition. A typical example is A historical table where only the current month 's data is updatable and the other 11 up are read only.