Feature request; Internals Viewer 2 Beta 1 20081215

Dec 16, 2008 at 4:19 PM
Hi Danny,

I've been using IV for sometime now and i like it.... A LOT!!!

But being a dutchman, i have a few ideas for some features:


  • In page viewer a selection mechanism that allows to select a table or index and a next step button to follow the doubely linked list.
  • A navigatable pyramid like view of the B-tree structure of an index

Both of these would grately contribute to the insight of the database storage engine, especially in training situations.

NExus64 / Theo

Dec 16, 2008 at 7:33 PM

I'm glad you like the app!

Thanks for the suggestions.

You can navigate the double linked lists. The Next Page and Prev. Page addresses can be clicked to change the page. Did you have something else in mind?

The pyramid thing is a great idea. I'll have a think about how it can be achieved.


Dec 17, 2008 at 11:44 AM
Edited Dec 17, 2008 at 11:46 AM

Hi Danny

I had the impression that the next button navigated to the next page as in 1:1 to 1:2 to 1:3, but now you are saying that it navigates the doubely linked list by default?

It might be an idea to make it optional to use the doubely linked list when clicking next/prev, so you can choose to go to the next page in order or the next page on the doubely linked list.

For the pyramid i would suggest a treeview like functionality rotated 90 degrees so you can see something like this

        +            +   .....
    int    int    int    int ..... summary of int level; #index rows, #pages, page density, etc
      +    +    +    +    .....
    int    int    int    int ..... summary of int level; #index rows, #pages, page density, etc
      +    +    +    +    .....
   L L L L L L L L ..... summary of leaf level; #index rows, #pages, page density, etc

                |  ---- split window?

The leaf entry should hotlink to the correspondending data page

As far as the visual layout is concerned  the 3rd and 4th levels couldbe quite wide, so horizontal scrollbars will be needed, split view might then be an idea so you can see the first and the last leaf page simultaniously..?

In the root and intermediate pages i would only show a preview of the first and last index key of that page row so the pyramid's height would stay limited

Maybe use a synced 2 window frame solution, where the left window shows the pyramid and the right window the decoded page?

And for the usage of this app; i use it while training our new DBA's and programmers so they can see what really happen. A picture has more worth than a thousand words.   ;)

Nexus64 / Theo