Help!!!!!! How to design the Oracle management mode and method of historical data?? Bosses give some opinions!!! Urgent!!!! River's lake emergency!!!!!!

CodePudding user response:

Table, depots, separation, speaking, reading and writing,

CodePudding user response:

The partition table, or renamed

CodePudding user response:

Can elaborate on it

CodePudding user response:

The

reference 3 floor who am I? Who is me? Response:

can you specific a bit

Take a chestnut:
Since historical data, so the "historical" surely can be defined by a certain time field, according to the time field (usually also query the upper application often or will use to the time field) will table partition, because oracle partition support drop, truncate, exchange and other operations, you can according to your favorite way to deal with those in accordance with the standards of zoning fields, can be classified as "historical data partition of the data,"
Design time is important to note: the partition table index should adopt what kind of type, global index? Or local indexes, because in the division after the drop, truncate operation, such as global index partition table will fails, you may need to be in the operation of the partition, coupled with the update global indexes clause to ensure that the index will failure (partition operating rate dropped significantly, of course), or in the division operation is completed, rebuild the failure of the global index,
Of course, you can use a local index, of course, when local index range scan consuming IO will be higher than the global index, busy OLTP systems, may choose to do,
In addition, about the index of local and global index, there are two limitations: 1, the bitmap index can only be local index; 2, if the primary key field does not contain the partitions, so the primary key index can only be global indexes,

CodePudding user response:

Aww thank you bosses