blocks|key|3751169|text|SQL+Server内置了创建GUID的功能。不需要为此编写单独的存储过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3751170|您可以使用|3751171|3751172|blockquote|3751173|3751174|3751175|NEWID()|unordered-list-item|offset|length|3751176|NEWSEQUENTIALID()|3751177|3751178|这两个过程之间的关键区别在于，如果GUID用于主聚集键，则应使用顺序GUID。|3751179|我不知道为什么您希望数据库引擎记住以前生成的GUID。|3751180|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa276822%2528SQL.80%2529.aspx|1|http://msdn.microsoft.com/en-us/library/ms189786.aspx^0|0|0|0|0|0|0|0|7|0|0|0|H|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|E|3|-4|5|F|7|17|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1A|8|@]|9|@$L|1B|M|1C|1|1D]]|A|$]]|$1|N|3|O|5|K|7|1E|8|@]|9|@$L|1F|M|1G|1|1H]]|A|$]]|$1|P|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]]]

SQL Server has the creation of GUID's built in. There is no need to write a separate stored procedure for this. 

You can use

<blockquote>
 <ul>
 <li><a href="http://msdn.microsoft.com/en-us/library/aa276822%28SQL.80%29.aspx" rel="noreferrer">NEWID()</a></li>
 <li><a href="http://msdn.microsoft.com/en-us/library/ms189786.aspx" rel="noreferrer">NEWSEQUENTIALID()</a></li>
 </ul>
</blockquote>

The key difference between both procedures would be that the sequential GUID should be used if it is for a primary clustered key.

I'm not sure why you would want the database engine to remember the previous generated GUID.

blocks|key|3751141|text|不，你的假设是错误的:数据库将不会记住任何东西-所以从这个角度来看没有任何好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3751142|如果您使用GUID作为SQL+Server中的主键/聚集键，这从一开始就不是一个好主意(请参阅here、here或here为什么是这样)，您至少应该使用+newsequentialid()函数作为对该列的默认约束。|offset|length|style|CODE|3751143|CREATE+TABLE+YourTable(ColumnA+uniqueidentifier+DEFAULT+NEWSEQUENTIALID())+|code-block|syntax|javascript|3751144|这样，数据库将为您的PK生成伪序列GUID，从而使使用GUID作为PK/CK的负面影响至少可以承受……|3751145|如果您没有使用GUID作为主键，那么我真的看不出在服务器上创建GUID有什么好处。|3751146|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sqlskills.com/BLOGS/KIMBERLY/post/GUIDs-as-PRIMARY-KEYs-andor-the-clustering-key.aspx|1|http://sqlskills.com/BLOGS/KIMBERLY/post/The-Clustered-Index-Debate-Continues.aspx|2|http://www.sqlskills.com/BLOGS/KIMBERLY/post/Ever-increasing-clustering-key-the-Clustered-Index-Debateagain!.aspx|3|http://msdn.microsoft.com/en-us/library/ms189786.aspx^0|0|25|H|1B|4|0|1G|4|1|1L|4|2|25|H|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@$D|18|E|19|1|1A]|$D|1B|E|1C|1|1D]|$D|1E|E|1F|1|1G]|$D|1H|E|1I|1|1J]]|A|$]]|$1|H|3|I|5|J|7|1K|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1L|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]|12|$5|T|U|V|A|$W|13]]]]

No, your assumption is wrong: the database won't be remembering anything - so there's no benefit from that point of view.

If you're using the GUID as your primary key / clustering key in SQL Server, which is a bad idea to begin with (see <a href="http://www.sqlskills.com/BLOGS/KIMBERLY/post/GUIDs-as-PRIMARY-KEYs-andor-the-clustering-key.aspx" rel="noreferrer">here</a>, <a href="http://sqlskills.com/BLOGS/KIMBERLY/post/The-Clustered-Index-Debate-Continues.aspx" rel="noreferrer">here</a> or <a href="http://www.sqlskills.com/BLOGS/KIMBERLY/post/Ever-increasing-clustering-key-the-Clustered-Index-Debateagain!.aspx" rel="noreferrer">here</a> why that's the case), you should at least use the <a href="http://msdn.microsoft.com/en-us/library/ms189786.aspx" rel="noreferrer"><code>newsequentialid()</code></a> function as default constraint on that column.

<pre><code>CREATE TABLE YourTable(ColumnA uniqueidentifier DEFAULT NEWSEQUENTIALID()) 
</code></pre>

That way, the database would generate pseudo-sequential GUID's for your PK and thus would make the negative effects of using a GUID as PK/CK at least bearable....

If you're not using the GUID as your primary key, then I don't see any benefit in creating that GUID on the server, really.

blocks|key|688033|text|我更喜欢在应用程序中创建GUID，而不是在数据库中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|688034|688035|简化了插入后检索行的过程。更轻松的域/业务层单元testing.|unordered-list-item|688036|Faster.+|688037|至少对于实体框架是这样的。http://blogs.msdn.com/b/adonet/archive/2010/06/28/performance-impact-of-server-side-generated-guids-in-ef.aspx|offset|length|688038|688039|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/adonet/archive/2010/06/28/performance-impact-of-server-side-generated-guids-in-ef.aspx^0|0|0|0|0|D|32|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Y|8|@]|9|@$J|Z|K|10|1|11]]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

My preference is to create GUID in the application not the db.

<ul>
<li>Simplifies the retrieval of rows after insertion. </li>
<li>Easier domain/business layer unit testing.</li>
<li>Faster. At least for entity framework. <a href="http://blogs.msdn.com/b/adonet/archive/2010/06/28/performance-impact-of-server-side-generated-guids-in-ef.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/adonet/archive/2010/06/28/performance-impact-of-server-side-generated-guids-in-ef.aspx</a></li>
</ul>

blocks|key|2343208|text|RFC41221：不要假设UUID很难猜测；例如，它们不应该用作安全功能(仅拥有就可以访问的标识符)。一个可预测的随机数来源将使情况恶化»。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2343209|在简单的任务中，增量uint64更好。|2343210|不使用GUID！如果需要安全的话。|2343211|http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/b37b3438-90f4-41fb-adb9-3ddba16fe07c|2343212|entityMap|0|LINK|mutability|MUTABLE|url|1^0|7|1|0|0|0|0|0|2N|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|I]]|Q|$5|M|N|O|C|$P|I]]]]

RFC4122<a href="http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/b37b3438-90f4-41fb-adb9-3ddba16fe07c" rel="nofollow">1</a>: «Do not assume that UUIDs are hard to guess; they should not be used as security capabilities (identifiers whose mere possession grants access), for example. A predictable random number source will exacerbate the situation». 

In simple task incremental uint64 better.

NOT USE GUID! If need security. 

<a href="http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/b37b3438-90f4-41fb-adb9-3ddba16fe07c" rel="nofollow">http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/b37b3438-90f4-41fb-adb9-3ddba16fe07c</a>

I am thinking to use a GUID in my .net app which uses SQL Server. Should I be writing a stored procedure which generates the GUID on each record entered or should I be directly generating it from the application.

Reasons for asking the question (If am wrong correct me in this):

I (as/pre)sume:

When generating the GUID from the database, you can assume that the DB remembers the previous generated GUID where as the application remembering it is difficult.

Generating GUID

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在考虑在我的使用SQL Server的.net应用程序中使用GUID。我是应该编写一个存储过程来在输入的每个记录上生成GUID，还是应该直接从应用程序生成它。问这个问题的原因(如果我错了，请纠正我)：I (as/pre)sume：当从数据库生成GUID时，您可以假设DB记住了以前生成的GUID，因为应用程序很难记住它。

问生成GUID
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问生成GUIDEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问生成GUID
EN