I saw in your other reply that you abort after 300 records. Does the performance get worse as more and more records are inserted?
>The tables I am working on at the moment are empty so it shouldn't have any effect on the speed when SQL Server reindexes. I have had a suggestion that the link may slow it down but I am using a dedicated LAN with just the server and one PC with nothing else attached. The clustered (primary) index is on the identity column and there is only one other index.
>
>>If you're going to do large bulk inserts like that, you should drop all indexes on the table, do the inserts and then recreate the indexes. SQL Server reindexes the table with every insert and this can cause the performance hit you mention.
>>
>>HTH
>>
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
