I am hitting some performance bottlenecks with my C# client inserting bulk data into a SQL Server 2005 database and I\'m looking for ways in which to speed up the process.>
My guess is that you'll see a dramatic improvement if you change that index to be nonclustered. This leaves you with two options:
Either one will speed up your inserts without noticeably slowing down your reads.
Think about it this way -- right now, you're telling SQL to do a bulk insert, but then you're asking SQL to reorder the entire table every table you add anything. With a nonclustered index, you'll add the records in whatever order they come in, and then build a separate index indicating their desired order.