文本(blob)比 varchar/nvarchar 的效率低多少? [英] How much more inefficient are text (blobs) than varchar/nvarchar's?

问题描述

我们正在为一个相当大的项目(大约有 600 名用户全天使用它 - 至少对我来说很重要;-))制作了很多大而简单的表单.

We're doing a lot of large, but straightforward forms for a fairly big project (about 600 users using it throughout the day - that's big for me at least ;-) ).

表格有很多问题/答案类型的部分，所以有些人很自然地输入句子，而另一些人则输入小说.对其中一些字段设置字符限制有什么好处真的?

The forms have a lot of question/answer type sections, so it's natural for some people to type a sentence, while others type a novel. How beneficial would it be to put a character limit on some of these fields really?

(如有必要/可能，请包括参考文献或引文 - 谢谢！)

(Please include references or citations, if necessary/possible - Thanks!)

推荐答案

如果您对数据大小没有限制，那何必担心.这听起来不像是一个关键任务项目，即使有 600 个用户和数千条记录.使用 CLOB/BLOB 并完成它.我怀疑您是否会在限制大小和冒数据丢失风险方面看到任何重大收益.也就是说，您应该在实施之前布置这些边界.

If you have no limitations on the data size, then why worry. This doesn't sound like a mission critical project, even with 600 users and several thousand records. Use CLOB/BLOB and be done with it. I have doubts as to whether you would see any major gains in limiting sizes and risking data loss. That said, you should layout such boundaries before implementation.

通常 varchar 最适合存储您希望在逻辑上使用的值并对其执行全值"比较.文本用于非结构化数据.如果您的项目是非结构化文本的调查结果，请使用 CLOB/BLOB

Usually varchar is best for storing values that you wish to use logically and perform "whole value" comparisons against. Text is for unstructured data. If your project is a survey result with unstructured text, use CLOB/BLOB

半参考:我处理数十万个呼叫中心记录，有时我们使用 CLOB 来存储员工和客户之间的对话.

Semi-Reference: I work with hundreds of thousands of call center records sometimes where we use a CLOB to store the dialog between employees and customers.

这篇关于文本(blob)比 varchar/nvarchar 的效率低多少?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！