the user of the script should:
  create a database called mydb
  create the tables you are interested in into mydb 
  (or grab them all using dbschema )

run the script.
after that
fill in the # of rows to be expected into the table mysize  including 
the tablename

select * from total_size;
will give you the size needed per table; see the comments in the script.

This was created long time ago for V7.
V9 gives a -999 on select * from <db>:sysindexes. therefor it's called 
size9.sql
in order to get around that. ahum whilst writing this i saw

mysize.tablename char(18)

This should be

mysize.tablename char(128)


Superboer.





----- Oorspronkelijk bericht -----
Van: Obnoxio The Clown <obnoxio@serendipita.com>
Datum: woensdag, december 7, 2005 9:15 am
Onderwerp: Re: size9

> 
> Peter Wages said:
> >
> > Obnoxio -
> >
> >      Thank you for submitting size9.  Please review
> > http://www.iiug.org/software/repository_news.html to verify  
> that i have
> > described things correctly.
> 
> Hi,
> 
> Probably better if superboer does it -- he wrote it! :o)
> 
> -- 
> Bye now,
> Obnoxio
> 
> "C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
>  - Coluche
> 
> did i mention i like nulls? heck, i even go so far as to say that all
> columns in a table except the primary key could/should be 
> nullable. this
> has certain advantages, for example, if you need to insert a child 
> recordand you don't have a parent row for it, just do an insert 
> into the parent
> table with the primary key value (everything else null), and voila,
> relational integrity is preserved. but this is, admittedly, a bit
> controversial among modellers.
> 
> --r937, dbforums.com
>