You can export the statistics and import back after you import the actual d= ata. While doing import, the ANALYZE=3DY should also do the analyze. On 5/5/05, bill thater <shrekdba@xxxxxxxxx> wrote: > solaris 9 > 9.2.0.6 >=20 > OK i have several development databases here. the production ones are > someplece else and they're not my concern yet. a lot of the > evelopment here consists of truncating and reloading tables in a > couple of schemas on the databases, adding data, importing data. most > of the schemas are static. this leads to developers showing up at my > cube and <whiney voice> "bill, the database is slow again.</whiney > voice>. most of this can be fixed by just gathering stats on those > schemas. >=20 > so what i'm looking for is pointers to TFM, white papers, best > pratices, your favorite method of gathering stats on just those > schemas so i can write a script to be chroned to run against them. >=20 > thanks. >=20 > --=3D20 > -- > Bill "Shrek" Thater ORACLE DBA =3D20 > shrekdba@xxxxxxxxx=3D20 > ------------------------------------------------------------------------ > om mani padme hum > -- > //www.freelists.org/webpage/oracle-l >=20 --=20 Regards Zhu Chao www.cnoug.org -- //www.freelists.org/webpage/oracle-l