Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!voder!blia!nobody
From: nobody@blia.sharebase.com (Nobody at all)
Newsgroups: comp.databases
Subject: Re: Sybase bulk copy strangeness
Message-ID: <13543@blia.sharebase.com>
Date: 21 Feb 91 17:28:10 GMT
References: <6851@tantalum.UUCP>
Reply-To: jeffb@blackhaw.UUCP (Jeff Beard)
Organization: ShareBase
Lines: 13

You failed to mention if there are any secondary indices on the
table.  Many systems allow creation of secondary indices after
the fact, which makes the initial bulk load run significantly
faster.  There is a large overhead associated with updating
secondary indices during a massive load.  When done as an
adjunct task after the load, the internal sort and/or block
splits for the index are avoided, and the cost of the
bulk load + secondary create and load < bulk load with secondary indices.

Observations from QBE.


J.O.Beard   jeffb@sharebase.com


Brought to you by Super Global Mega Corp .com