Posted by Dan Guzman on 03/11/06 21:29

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9783C8934F974Yazorman@127.0.0.1...
> Case-insensitive collation on SQL 2000 and case-sensitive on SQL 2005?

Both instances are SQL_Latin1_General_CP1_CI_AS.

> Somehow, the only way I could see that this sequence could lead to
> this error is that either the DELETE is incompletes with the incoming
> data, or the incoming data itself has duplicates. I've seen many weird
> bugs, but that DELETE would not have completed when the next statement
> runs sounds a little fantastic to me.

Perhaps the delete completed but there was something left over
(temporarily?) by DELETE that BULK INSERT was sensitive to due to the
transaction. TRUNCATE is more thorough than delete. Maybe the problem is
data-dependent as well. I hope OP can come up with a repro for my peace of
mind.

> But I've been wrong before.

Make's two of us ;-)

--
Hope this helps.

Dan Guzman
SQL Server MVP

[Back to original message]