RE:Re: DBIMPORT and indexes

In article <806690413snz@excelsis.demon.co.uk> Sally Woolrich <Sally@excelsis.demon.co.uk> writes: >In article <3v1r5d$6lk@tattoo.sccsi.com> > goldberg@landata.com "Steve Goldberg" writes: >> Question: >> When doing a dbimport after a dbexport, and leaving the .sql as is, >> will the dbimport load all the data for a table and then build the >> indexes? Or will it build the indexes as it loads the data? (Which we >> all know is a slow way to do it) >I'd like to know the answer to this too, though it's a bit >academic since it does what it does. But I do know that it's >much, much, much faster to do the 'dbimport' with transaction logging >turned of and to start it once the import has finished! >-- >============================================================================ >Sally Woolrich | This mail contains my personal >sally@excelsis.demon.co.uk | views not those of my employer! >============================================================================ During dbimport the table is created, data is loaded, and then the indexes for that table are created, it is all done sequentially per table.