Chaining row problem resolving
Hello,
I have following analyze data on some table:
Num_Rows =16201970, chain_cnt=2479288, avg_row_len = 254, avg_space = 843, pct_free = 10%, db_block_size = 2K
1. 2mio of chained rows per 16mio rows -> decision for eliminating the chained/migrated rows
1.1 Here I am considering the problem of having 13 indexes on that tables that
1.1.1 estimate of delete operation of chained rows during the procedure ....time costly operation for night or weekend?
1.1.2 re-correcting indexes after delete operation because of
- fragmentation and index degeneration
2. avg_space = 843, avg_row_len = 254, pct_free= 10 -> decision for raising pct_free to improve future updates,deletes for lower migration of rows
I have following analyze data on some table:
Num_Rows =16201970, chain_cnt=2479288, avg_row_len = 254, avg_space = 843, pct_free = 10%, db_block_size = 2K
1. 2mio of chained rows per 16mio rows -> decision for eliminating the chained/migrated rows
1.1 Here I am considering the problem of having 13 indexes on that tables that
1.1.1 estimate of delete operation of chained rows during the procedure ....time costly operation for night or weekend?
1.1.2 re-correcting indexes after delete operation because of
- fragmentation and index degeneration
2. avg_space = 843, avg_row_len = 254, pct_free= 10 -> decision for raising pct_free to improve future updates,deletes for lower migration of rows
0