Re: dbexport/dbimport problems

On Wed, 25 Jan 1995, jerry wrote: > If I am not mistaken, the default location for a table is the same > dbspace as the database was created it, this is not always the > root dbspace. True. To clarify, If you create a database without explicity specifying a dbspace, it ends up in the root dbspace. When you create a table it ends up in the same dbspace as the database is in, unless you specify otherwise. If you do a dbexport/dbimport and do not specify the "-d dbspace_name" option on the dbimport, the database that you are importing will end up in the root dbspace, along with all of its tables. If you do specify a dbspace to dbimport, the database and all of its tables will be created in that dbspace. In many cases, as a performance optimization, people will explicitly position tables in different dbspaces, on different physical disks, to minimize the ammount of contention for the disks. Doing a dbexport/dbimport will loose this optimization, unless you manually edit the sql file created by dbexport. Joe Matuscak Rohrer Corporation 717 Seville Road Wadsworth, Ohio 44281 (216)335-1541 Matuscak@Rohrer.com