Alex Black wrote: > > If you just want to check the current size of a table, use: > > SELECT NUMERIC_VALUE from SYSDBA.TABLESTATISTICS > > WHERE owner = <the owner of the > table you want to > > check> > > AND tablename = <the tablename of the > table you want > > to check> > > AND description = 'Used pages' > > Ok, but how do I allow for growing data sets given that I > need to specify > the 'size' of a devspace? > > Do I just specify MAXDEVSPACES to something high like 50? > > I basically did that: > > I created a devspace with 100000 data pages, and set > MAXDEVSPACES to 100.
??? Mhm, there seems to be a big misunderstanding. If you just specify ONE devspace with 100 000 pages, i.e. tell the kernel DEVSPACE_NAME and DEVSPACE_SIZE, then your database has not more than 100 000 pages, no matter how many devspaces you COULD have specified. This maximum number is given by MAXDEVSPACES. But the kernel is not able, not allowed (how should it do it?) to say, 'ok, those pages whose number (100 000) I know and of which I know the name of the devspace are full, lets create a new file or raw device somewhere on the users disks, name it somehow, specify a size I, the kernel, would like and fill it.' If the database, i.e. the number of specified devspaces, each with name and size, is full, the USER/ADMINISTRATOR of the database has to decide, where and how much additional disk-space the database may use. And, what seems to be important to understand: Each table/index/meta-data of the database is allowed to be stored at ANY devspace used for this database. It is spread over all devspaces available. Therefore it does not matter if you have 50 devspaces each with 100 000 pages or one huge devspace if you want to store a table which will need much more than those 100 000 pages available on ONE small devspace. Things are a little bit different to Oracle. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
