Posted by Dan Guzman on 03/13/06 15:16

Thanks for taking the time to put together a repro. I hope you have more
success than I did.

FWIW, I tested with SQL 2000 SP4 Developer edition
(SQL_Latin1_General_CP1_CI_AS) on a dual core XP box. The only commonality
with your system are SQL 2000 and dual CPUs. I did not experience the
problem when I omitted the explicit transaction.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Ryan" <ryanofford@hotmail.com> wrote in message
news:1142242811.722408.171710@u72g2000cwu.googlegroups.com...
> I'll get the code together and post some more meaningful detail in a
> short while.
>
> Just for further information, the collation is Latin1_General_CI_AS and
> it's on SQL2000 SP3. It's running on Windows 2000AS SP4, 2 Xeon 3.2Ghz,
> 2GB RAM.
>
> We've tried this step by step and have thoroughly checked the data and
> there are no duplicates. As I mentioned originally, it works fine if
> you delete the data, then add after a short while, which made finding
> this a little tricky. Running the two together causes the violation.
> What was done was the deletion, then try the bulk insert, if the bulk
> insert fails, it tries to insert line by line, which in effect causes a
> slight delay, which seems sufficient to allow it to work.
>
> I'll post the code and the DDL shortly.
>
> Ryan
>

[Back to original message]