sql - Azure 数据传输身份列种子跃升 10,000

Question

通过sql脚本插入数据后那个有

SET IDENTITY_INSERT [dbo].[table] ON
...
SET IDENTITY_INSERT [dbo].[table] OFF

身份种子增加了10000

我尝试过运行重新种子

dbcc CHECKIDENT ('vendors', 'reseed', 57439)

但我收到错误消息，指出此版本的 SQL Server 不支持 DBCC 命令“CHECKIDENT”。

以后如何杜绝这个问题？

Answer 1

我找到了this post在网络上。

The behavior (reseed) is by design, but has been acknowledged internally as less than optimal and a request has been made (again, internally) to change the behavior. This may or may not happen.

The reseed is triggered by instance bounces, which are covered by the SLA. They are mostly patches to the OS or SQL Azure itself.

The most important point was that, chances are, we will never hit the int limit. I think we all are forgetting (at least I did) that SQLAzure is not like SQL Server; there are very real limits in place, specifically total db size (150 gigs). He also said there is a max row limit per table of 10 million records, but I'm not finding documentation of that on the web. Assuming that is correct, even with jumps of 1000k, we would still be safe. And yes you could also switch to a bigint if you hit the int limit before the total db size limit. His point was simply that we will run out of room before we hit the int limit.

SQL Azure 上的限制可能会改变，但我想重点是，如果 SQL 实例崩溃，您可能会遇到很大的差距。