Identity out of sync after unexpectedly shut down

[Tania]

I have 2 DB on SQL Server 7, that are synchronized by a continuous transactional replication.
The tables have a primary key on an identity column. In order to avoid conflicts,
the identities have different seeds, and increment equal to 10.
When the server shuts unexpectedly, the current value for the
identity column goes out of sync, that is it assumes the greatest value inserted.
The workaround is to run DBCC checkident to correct the identity value.

Is it a bug? Did anyone run in the same problem?

TIA
Tania

[Craig]

It was that way in 6.5 as well........


------------
Tania at 1/11/00 4:31:04 AM

I have 2 DB on SQL Server 7, that are synchronized by a continuous transactional replication.
The tables have a primary key on an identity column. In order to avoid conflicts,
the identities have different seeds, and increment equal to 10.
When the server shuts unexpectedly, the current value for the
identity column goes out of sync, that is it assumes the greatest value inserted.
The workaround is to run DBCC checkident to correct the identity value.

Is it a bug? Did anyone run in the same problem?

TIA
Tania

[deepak]

I think is a famous 3627 error in SQL Server. ( You can get a sp to fix this everytime it occurs somewhere in MS web site. )

deepak.
------------
Craig at 1/11/00 8:31:53 AM

It was that way in 6.5 as well........


------------
Tania at 1/11/00 4:31:04 AM

I have 2 DB on SQL Server 7, that are synchronized by a continuous transactional replication.
The tables have a primary key on an identity column. In order to avoid conflicts,
the identities have different seeds, and increment equal to 10.
When the server shuts unexpectedly, the current value for the
identity column goes out of sync, that is it assumes the greatest value inserted.
The workaround is to run DBCC checkident to correct the identity value.

Is it a bug? Did anyone run in the same problem?

TIA
Tania