Azure 数据传输标识列种子跃升 10,000 [英] Azure data transfer Identity Column Seed Jumped by 10,000

查看:20
本文介绍了Azure 数据传输标识列种子跃升 10,000的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

通过sql脚本插入数据后有

After inserting the data via sql script that had

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

身份种子增加了10,000

the identity seed has increased by 10,000

我试过运行 reseed

I have tried running reseed

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

但我收到错误消息,指出此版本的 SQL Server 不支持 DBCC 命令CHECKIDENT".

but I get the error saying the DBCC command 'CHECKIDENT' is not supported in this version of SQL Server.

以后如何解决这个问题?

How to stop in the future this problem?

推荐答案

I found 网络上的这篇帖子.

行为(reseed)是有意为之,但已被承认内部不是最优的并且已经提出请求(再次,内部)来改变行为.这可能会也可能不会发生.

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.

重新种子由实例反弹触发,由服务水平协议.它们主要是操作系统或 SQL Azure 本身的补丁.

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

最重要的一点是,很有可能,我们永远不会击中整数限制.我想我们都忘记了(至少我忘记了)SQLAzure 与 SQL Server 不同;有非常实际的限制,特别是总数据库大小(150 演出).他还说有一个max row每表限制 1000 万条记录,但我没有找到网络上的文档.假设这是正确的,即使跳跃 1000k,我们仍然是安全的.是的,你也可以切换如果在总数据库大小限制之前达到 int 限制,则为 bigint.他的观点很简单,我们将在到达终点之前用完空间.整数限制.

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 实例崩溃,你会得到很大的差距.

The Limits on SQL Azure could change, but I guess the point is you can get the large gaps if the SQL instance crashes.

这篇关于Azure 数据传输标识列种子跃升 10,000的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆