blocks|key|3502780|text|这取决于你在做什么：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3502781|3502782|如果速度是首要问题，那么普通的老式int可能就足够大了。|unordered-list-item|offset|length|style|CODE|3502783|如果您确实要有超过20亿条(带B+;)的记录，则使用bigint或顺序guid。|3502784|如果您需要能够轻松地与远程创建的记录进行同步，则Guid确实很棒。<代码>H29<代码>F210|3502785|3502786|更新|BOLD|3502787|有关Guids的其他(不太明显)说明：|3502788|performance|3502789|You+|3502790|它们对索引的要求可能很高，而且切入数据库核心的guids可以使用顺序guids来恢复一些索引性能，但放弃了第二点中使用的一些随机性。|3502791|guids可能很难手动调试(where+id='xxx-xxx-xxxxx')，但您也可以通过顺序guids+(where+id='xxx-xxx'+%2B+'123')获得一些恢复。|3502792|出于同样的原因，Guids可以使基于ID的安全攻击变得更加困难-但并非不可能。(你不能只输入'http://example.com?userid=xxxx'，然后期望得到别人账户的结果)。|3502793|3502794|3502795|entityMap^0|0|0|H|3|0|Q|6|0|O|4|0|0|0|2|0|0|0|0|0|E|O|1K|Q|0|1A|W|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@$F|1A|G|1B|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|1F|8|@$F|1G|G|1H|H|I]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1J|8|@$F|1K|G|1L|H|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1M|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|1O|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|1P|8|@]|9|@]|A|$]]|$1|Z|3|10|5|E|7|1Q|8|@$F|1R|G|1S|H|I]|$F|1T|G|1U|H|I]]|9|@]|A|$]]|$1|11|3|12|5|E|7|1V|8|@$F|1W|G|1X|H|I]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|16|$]]

That depends on what you're doing: 

<ul>
<li>If speed is the primary concern then a plain old <code>int</code> is probably big enough.</li>
<li>If you really will have more than 2 billion (with a B ;) ) records, then use <code>bigint</code> or a sequential guid.</li>
<li>If you need to be able to easily synchronize with records created remotely, then <code>Guid</code> is really great.</li>
</ul>

Update 
Some additional (less-obvious) notes on Guids:

<ul>
<li>They can be hard on indexes, and that cuts to the core of database performance</li>
<li>You can use sequential guids to get back some of the indexing performance, but give up some of the randomness used in point two.</li>
<li>Guids can be hard to debug by hand (<code>where id='xxx-xxx-xxxxx'</code>), but you get some of that back via sequential guids as well (<code>where id='xxx-xxx' + '123'</code>). </li>
<li>For the same reason, Guids can make ID-based security attacks more difficult- but not impossible. (You can't just type <code>'http://example.com?userid=xxxx'</code> and expect to get a result for someone else's account).</li>
</ul>

blocks|key|3502750|text|一般来说，我会推荐BIGINT而不是GUID+(因为guids又大又慢)，但问题是，你真的需要它吗？(例如，您是否正在进行复制？)如果您期望的行数少于20亿行，那么传统的INT就足够了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3502751|entityMap^0|9|6|I|4|2D|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

In general I'd recommend a <code>BIGINT</code> over a <code>GUID</code> (as guids are big and slow), but the question is, do you even need that? (I.e. are you doing replication?)
If you're expecting less than 2 billion rows, the traditional <code>INT</code> will be fine.

blocks|key|285871|text|如果您正在进行复制，或者您的销售人员正在运行需要合并的断开连接的数据库，请使用GUID。否则我会选择int或bigint。从长远来看，它们更容易处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285872|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Are you doing replication or do you have sales people who run disconnected databses that need to merge, use a GUID. Otherwise I'd go for an int or bigint. They are far easier to deal with in the long run.

blocks|key|4350274|text|并不取决于你需要什么。DB+Performance将从整数中获益，而GUID对于replication很有用，并且不需要从数据库了解已创建的标识，即代码可以在插入行之前创建GUID标识。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4350275|entityMap^0|E|B|14|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Depends no what you need. DB Performance would gain from integer while GUIDs are useful for replication and not requiring to hear back from DB what identity has been created, i.e. code could create GUID identity before inserting into row.

blocks|key|285838|text|如果您计划使用合并复制，那么ROWGUIDCOL对性能(see+here+for+info)是有好处的。否则，我们需要更多关于你对“更好”的定义的信息；更好是为了什么？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|285839|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms152770.aspx^0|E|A|S|H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

If you're planning on using merge replication then a <code>ROWGUIDCOL</code> is beneficial to performance (<a href="http://msdn.microsoft.com/en-us/library/ms152770.aspx" rel="nofollow noreferrer">see here for info</a>). Otherwise we need more info about what your definition of 'better' is; better for what?

blocks|key|3503062|text|使用GUID可能会有更多的方面或要求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3503063|3503064|如果主键是任何数字类型(Int、BigInt或任何其他类型)，则需要将其设置为Identity列，或者需要检查表中最后保存的值。|unordered-list-item|3503065|，在这种情况下，如果外表中的记录另存为事务，则很难获得主键的最后一个标识值。例如，如果使用IDENT_CURRENT，则在外键中保存记录时会再次影响性能。|3503066|因此，在将记录保存为事务的情况下，首先为主键生成Guid，然后将生成的键(Guid)保存在主表和外表中。|3503067|3503068|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

There can be few more aspects or requirements to use GUID.

<ul>
<li>If the primary key is of any numeric type (Int, BigInt or any other), then either you need to make it Identity column, or you need to check the last saved value in the table.</li>
<li>And in that case, if the record in foreign table is saved as transaction, then it would be difficult to get the last identity value of primary key. Like if IDENT_CURRENT is used, then will be again effect performance while saving record in foreign key.</li>
<li>So in case of saving the records as for transactions, then it would be convenient to firstly generate Guid for primary key, and then save the generated key (Guid) in primary and foreign table(s). </li>
</ul>

blocks|key|4350225|text|这真的取决于传入的信息是否以某种方式是连续的。我强烈建议用户使用GUID可能更好。但对于顺序数据，例如订单或其他需要容易排序的数据，bigint可能是更好的解决方案，因为它将被索引并提供快速排序，而不需要另一个索引的成本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4350226|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It really depends on whether or not the information coming in is somehow sequential. I highly recommend for things such as users that a GUID might be better. But for sequential data, such as orders or other things that need to be easily sortable that a bigint may well be a better solution as it will be indexed and provide fast sorting without the cost of another index.

blocks|key|285779|text|这真的取决于你是否期望在图片中有复制。复制需要一个行UUID，所以如果你打算这样做，你最好提前做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|285780|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It really depends whether you're expecting to have replication in the picture. Replication requires a row UUID, so if you're planning on doing that you may as well do it up front.

blocks|key|1010398|text|除非您确实需要GUID，例如可以在任何地方生成键，而不仅仅是在服务器上，否则我将坚持使用基于整数的键。GUID的创建成本很高，并且使实际查看数据变得更加困难。另外，您是否曾尝试在SQL查询中键入GUID？太痛苦了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1010399|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unless you have a real need for a GUID, such as being able to generate keys anywhere and not just on the server, then I would stick with using INTEGER-based keys. GUIDs are expensive to create and make it harder to actually look at the data. Plus, have you ever tried to type a GUID in an SQL query? It's painful!

blocks|key|4350477|text|我和安德鲁·罗林斯在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4350478|现在你可以争论空间效率了。一个整数是多少，最多8个字节？guid将变得更长。|4350479|但我有两个首选的主要原因:可读性和访问时间。数字对我来说比GUID更容易(因为我总是可以很容易地找到下一条/前一条记录)。|4350480|至于访问时间，请注意，一些DB可能会在GUID方面开始出现大问题。我知道MySQL+(MySQL+InnoDB+Primary+Key+Choice:+GUID/UUID+vs+Integer+Insert+Performance)就是这种情况。对于SQL+Server来说，这可能不是什么大问题，但需要注意。|offset|length|4350481|我会说坚持使用INT或BIGINT。我认为您唯一需要GUID的时候是您要分发GUID的时候，并且出于安全原因不希望人们能够猜测其他记录的ID。|4350482|entityMap|0|LINK|mutability|MUTABLE|url|http://www.kccoder.com/mysql/uuid-vs-int-insert-performance/^0|0|0|0|17|20|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I'm with Andrew Rollings.

Now you could argue space efficiency. An int is what, 8 bytes max? A guid is going to much longer.

But I have two main reasons for preference: readability and access time. Numbers are easier for me than GUIDs (since I can always find the next/previous record easily). 

As for access time, note that some DBs can start to have BIG problems with GUIDs. I know this is the case with MySQL (<a href="http://www.kccoder.com/mysql/uuid-vs-int-insert-performance/" rel="nofollow noreferrer" title="title">MySQL InnoDB Primary Key Choice: GUID/UUID vs Integer Insert Performance</a>). This may not be much of a problem with SQL Server, but it's something to watch out for.

I'd say stick with INT or BIGINT. The only time I would think you'd want the GUID is when you are going to give them out and don't want people to be able to guess the IDs of other records for security reasons.

For SQL server is it better to use an uniqueidentifier(GUID) or a bigint for an identity column?

Is it better to use an uniqueidentifier(GUID) or a bigint for an identity column?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

对于SQL server，对标识列使用唯一标识符(GUID)还是bigint更好？

问对标识列使用唯一标识符(GUID)还是bigint更好？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对标识列使用唯一标识符(GUID)还是bigint更好？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对标识列使用唯一标识符(GUID)还是bigint更好？
EN