I found a strange problem when changing a seed for an indentity column (for replication). I have Test table with IDENTITY(1,1) column.
I run the following script: DBCC CHECKINDENT('[dbo].[Test]', RESEED, 1000001)
When I script the table I get again IDENTITY(1,1). But when I insert a new record, the new id is 10000001 as expected. Is such a behaviour normal or is it a bug in SQL Server 2012? I would expect that the script uses new value of the seed.
Mark