Re: fragmented system tables

Art S. Kagel wrote: > > Richard Stanford wrote: buncha stuff snipped.... > > > > What you can do is take a dbexport, go in and modify the schema to set the > > NEXT size for all the system tables at the top. This way, they all go into > > two extents, but hopefully no more. I never bothered to do any serious > > benchmarking of this, and usually don't do it, but it is (as far as I know) > > the only safe way of reducing extent sizes in system tables. > > > > Has anyone benchmarked this? I'd imagine better results in larger > > systems (1000+ tables, etc). > > This won't work either since the system tables are created along with > the database and are not contained in the schema file that dbexport > produces. > > Art S. Kagel I used to administer a database that had scads of stored procedures that generated lots of extents in SYSPROCPLAN and one other catalog table. I used to routinely dbexport, edit the schema so that after the tables loaded (and before the SP's got created) set the nextsize for the SYSPROC* tables real big to get fewer extents, then dbimport. I would guess that you could do the same thing here, just do it earlier in the schema file (like right after CREATE DATABASE...). Worked like a champ for me. Greg