Re: Index created before load in dbimport

In article <mickmE1xBw4.MBt@netcom.com>, Mickey Mestel <mickm@netcom.com> writes >hi, > > this was discussed a while ago, and i seem to remember that a number of >people (myself included) were certain that indexes were *not* created before >the table is loaded in a dbimport. after all, that really doesn't make much >sense performance wise. > > today however, i was loading a fragmented table with the index in a >seperate dbspace. in looking around to try and see why it was so slow, i >noticed as much, if not more activity in my index dbspace. there were no other >threads running, so that wasn't a problem. > > by the way, it's a sparcstation 20, 5.5 solaris, 7.21 online. i was >really shocked to see this activity, and stopped the load. i then took that >create index out of the script, and sure enough, no activity in the index>dbspace during the load. that seemed to show it right there. > > so what is the story? am i missing something? is there a good reason >why something so seemingly obvious and idiotic is done this way? > > in general, although all stats look good, the system is loading >incredibly slow anyway. i seem to remember that from the last 7.x, solaris 5.x >site that i was at. anyone else? > > any comments? > > thanks, > > mickm > >-- > >_____________________________________________________________________________ >Mickey Mestel mickm@netcom.com > >-on a beach in thailand to a beautiful, stoned, norwegian woman: > "..yeah, it's just another foreign country without ice." >----------------------------------------------------------------------------- dbimport creates indicies then loads the data. (I think the sql file is normally something like:- create table.. create index.. create index.. ****************load table********************* The line with all the stars on it actually tells dbimport to load the table and it gets placed after the create index statements.... -- David Williams