It looks like rdb$pages only contains "important" pages needed by the engine, not a full catalogue
of all pages currently allocated. I was looking for a way to get an idea of how many pages each
table was using (data, index, and optionally blob?) to get an estimate of how space was being used
within a database (page size * number of pages, realizing lots of pages won't be completely full,
but also knowing that they still use space on disk even if not fully utilized). Since we can't
break out each table into an individual file, we can't just use the filesystem for that. Is there
some other way of doing this? Something other than taking the number of rows in the table * some
estimate of the row size? (I know Ann has written guides for estimating this, as part of her ODS
documentation, but I'm looking for "real size", not "maximum size".) I'm guessing there are some
tools that do this (some of the recovery tools, perhaps?) but can they be applied to a running
database?

Thanks!
-Philip