G
George Potemkin
Guest
Yes, idxblockreport exists since V9.0A. Is it get officially supported in the recent Progress versions? It has some issues (at least a couple) in past. I did not check if they are fixed now. Yes, it reports the information from the headers of index blocks - one line per block: >proutil sports2000 -C idxblockreport Customer.name OpenEdge Release 11.6 as of Fri Oct 16 19:02:26 EDT 2015 BlockSize = 4096 Block Capacity = 4068 Number Length On Length Delete of of Delete of Chain Percent DBKEY Level Entries Entries Chain Size Type Utilized 192 1 8 80 0 0 root 1 288 2 162 3197 0 0 leaf 78 544 2 142 3000 0 0 leaf 73 320 2 132 2919 0 0 leaf 71 576 2 144 3119 0 0 leaf 76 256 2 112 2464 0 0 leaf 60 672 2 124 2589 0 0 leaf 63 352 2 187 3004 0 0 leaf 73 512 2 115 2657 0 0 leaf 65 Index Block Report completed successfully. But dbrpr since V10, for example, can report the contents of /any/ db blocks but it does not make dbanalys utility obsolete. In most cases we need a summary report rather than the detailed information. Sometimes idxblockreport is very useful but it can't be a replacement for ixanalys. > it uses the idxcompact code and reports about the index and its blocks. When I said "it's not hard to implement" I meant that Progress already has all "ingredients" (codes) to implement a feature. I would not say that table partitioning was easy to implement. It has required very large changes in database structures and in the existent code. Nevertheless table partitioning was implemented. The "little features" are not required such large efforts from development. So it's a matter of the priorities. But personally I believe that "little things mean a lot". ;-) www.youtube.com/watch
Continue reading...
Continue reading...