Carl wrote:
> I am hoping that someone can point me in the right direction.  I need a
> utility that can map out how the primaries and secondaries are laid out in
a
> dataset.
snip
> HOWMESSY is cool but it does not show what we need.  The utility should
> layout a report that has the block and the layout of the primary records
and
> secondary records within it.  An example that we thought up would be:
>
> Block   Record
> 1       PPSSPSPPPSSPPPS
> 2       PP
> 3       PPS
> 4       PPSPSPPSSSSPP

Their was a utility called DBSTAT which printed a histogram for the entire
dataset. However this is quite ungainly for even a medium sized dataset.
HOWMESSY and DBLOADNG do address this issue with the Max Blks - which is the
worst case of contiguous full blocks. Given Image/SQL's mapped file IO this
number must be taken in combination with the block size to determine the
negative impact on performance. A small block can have a large max blks and
still fit into a single mapped file IO. OTH a large a large block can have a
smaller max blks that leads to additional IO.

At Beechglen.com in the freeware section we have an updated version of
DBLOADNG called DBLOADSX that has been updated to include the DDX, MDX, and
mapped file IO features of Image/SQL.

TGIF,

Mike Hornsby
Co-founder/Chief Technical Officer
Beechglen Development Inc. (beechglen.com)
513-922-0509
[log in to unmask]