Sometimes it is quicker to drop the indexes, do the inserts, and then create
the indexes again.
This of course depends on what else may be happening on your server at the
> of your data.Try loading the data after dropping the indexes. The above
> support a table lock option. Use that, as it further improves performance.
> Vyas, MVP (SQL Server)
> > We have a performance problem when inserting many rows into a table that
> > already keeps a very large amount of data on an SQL Server 2000 system.
> > table has four indexes (but no CLUSTERED).
> > Currently i am using an ADO Recordset Batchupdate but this has not been
> > improvement compared with the previously used precompiled INSERT
> > using an ADO Command object.
> > A few day ago i tied to improve performance using the Index Tuning
> > but as a result our application was much slower than before. Tuning
> > does not seem to be a solution.
> > Does anyone have an idea what can be done to improve the server
> > Which is the fastest way to get a large amount of data into a table?
> > Thanks in advance
> > Robert Knabe