基于已接受的答案，对于那些遇到类似问题的人，具有完整的模式限定:

([MyDataBase]。[MySchemaName]。[MyTable])……导致一个错误，您需要在该DB的上下文中

也就是说，下面的代码会抛出一个错误:

DBCC CHECKIDENT ([MyDataBase].[MySchemaName].[MyTable], RESEED, 0)

用单引号括起全限定表名:

DBCC CHECKIDENT ('[MyDataBase].[MySchemaName].[MyTable]', RESEED, 0)

重置数据库中的每个键，从最后一个最高键的最大值开始自动递增:

Exec sp_MSforeachtable 'DBCC CHECKIDENT(''?'', RESEED, 0)'

Exec sp_MSforeachtable 'DBCC CHECKIDENT(''?'', RESEED)'

如果你正在使用MySQL，试试这个:

ALTER TABLE tablename AUTO_INCREMENT = 1

基于已接受的答案，对于那些遇到类似问题的人，具有完整的模式限定:

([MyDataBase]。[MySchemaName]。[MyTable])……导致一个错误，您需要在该DB的上下文中

也就是说，下面的代码会抛出一个错误:

DBCC CHECKIDENT ([MyDataBase].[MySchemaName].[MyTable], RESEED, 0)

用单引号括起全限定表名:

DBCC CHECKIDENT ('[MyDataBase].[MySchemaName].[MyTable]', RESEED, 0)

半保证没有白痴:

declare @max int;  
select @max = max(key) from table;  
dbcc checkident(table,reseed,@max)

http://sqlserverplanet.com/tsql/using-dbcc-checkident-to-reseed-a-table-after-delete

You do not want to do this in general. Reseed can create data integrity problems. It is really only for use on development systems where you are wiping out all test data and starting over. It should not be used on a production system in case all related records have not been deleted (not every table that should be in a foreign key relationship is!). You can create a mess doing this and especially if you mean to do it on a regular basis after every delete. It is a bad idea to worry about gaps in you identity field values.