Identity corruption after 200-400 inserts???

Sql 2k, server has four dual-core processors. We're encountering an error
every 200-400 inserts that we are attempting to insert a duplicate row. The
table is simple:
BrokenIdentity
ID PK, identity
foo varchar
bar varchar
and so is the insert:
INSERT INTO BrokenIdentity (foo, bar) VALUES ('tar','fu')
but after about 200-400 inserts in a row we get the 'cannot insert duplicate
row' error. The rate this is happening is pretty shocking... the machine
isn't being shut down between the last good insert and the failing insert, s
o
that isn't the cause. Is this a common error with this type of modern
hardware? Are there any patches for this? Will setting the server to use
only one processor prevent this from happening? Does this also happen in
2k5? TIA.Are shure that is the only type of insert statement you use?
Milan
"William Sullivan" <WilliamSullivan@.discussions.microsoft.com> wrote in
message news:DDB9BB67-48B4-4478-B103-B88BE937ADB4@.microsoft.com...
> Sql 2k, server has four dual-core processors. We're encountering an error
> every 200-400 inserts that we are attempting to insert a duplicate row.
> The
> table is simple:
> BrokenIdentity
> ID PK, identity
> foo varchar
> bar varchar
> and so is the insert:
> INSERT INTO BrokenIdentity (foo, bar) VALUES ('tar','fu')
> but after about 200-400 inserts in a row we get the 'cannot insert
> duplicate
> row' error. The rate this is happening is pretty shocking... the machine
> isn't being shut down between the last good insert and the failing insert,
> so
> that isn't the cause. Is this a common error with this type of modern
> hardware? Are there any patches for this? Will setting the server to use
> only one processor prevent this from happening? Does this also happen in
> 2k5? TIA.