Re: dbschema and preserving extents and dbspaces.

Richard Johnson wrote: > > "Rajesh N. Malhotra" <malhotra@eos.ap.org> wrote: > > >InformiXperts, > > > The dbschema utility does not preserve the dbspace in wich the table > >lives, nor the extent sizes of the table. Some time back somebody had > >posted a utility that preserverd these values. Could someone point me to > >that utility? Does this utility take into account that tables might be > >fragmented? > > > Any and all help appreciated. > > >Thanx, > > >Raj. > > Try using the "-ss" option.... > > I normally use something like: > > dbschema -ss -t all -p all > myschema.out FYI: This is 7.x only; 5.x versions of the engine did not provide extent information (but since the original post talks about fragmenting, we suspect he *does* have 7.x, don't we). Also, I think using "> myschema.out" is going to put the dbschema stdout display (the paragraph with the version number and the like) in the output file. I think you can still list a file name at the end of the command without any argument flag: dbschema -ss -t all -p all myschema.out ... and the version verbiage will go to screen, and the schema will go to the file. //////////////// ======================================================= ////////// // Dennis J. Pimple Informix Software, Inc. ////// / /// Principal Consultant 5299 DTC Blvd Suite 740 ///// // //// dennisp@informix.com Englewood CO 80111 //// // ///// /// // ////// recept: 303-850-0210 // // /////// direct: 303-740-5611 Opinions expressed are mine, / /////////// fax: 303-843-6408 and do not necessarily //////////////// http://www.informix.com reflect those of my employer