blocks|key|1250361|text|在数据库中存储文件可以为您提供：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1250362|(%2B)更轻松的内部管理，磁盘上没有孤立文件|1250363|(%2B)一致的编程和访问模型(授权)|1250364|(-)数据库增长过快，会增加备份时间和保存备份文件所占用的磁盘空间|1250365|我不认为这两个选项的伸缩性都比另一个好。如果您预计会有非常多的文档，那么就会遇到目录中文件数量的限制(要么是作为绝对限制，要么是因为目录查找在某个点开始执行得非常差)。|1250366|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Storing files in the database gives you:

(+) easier house-keeping, no orphaned files on the disk

(+) consistent programming and access model (authorization)

(-) Database grows exorbitantly, which will increase backup time and disk space use to hold backup files

I don't think that either option scales better than the other. If you expect very large numbers of documents, you will hit limits regarding the number of files in a directory (either as an absolute limit, or because directory lookups begin to perform very poorly at a certain point).

blocks|key|3624626|text|将您的数据保存在数据库中将使管理日期变得更容易。您不必确保数据库中的数据与文件系统上的数据(文件路径)同步。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3624627|话虽如此，但重要的是要认识到，在数据库中存储大型blob时可能会影响性能。幸运的是，已经在这一领域进行了一些研究，以调查可能的情况。我建议你看看微软研究院关于这个问题的this+paper。希望这能有所帮助。|offset|length|3624628|此外，我应该提到的是，微软SharePoint将其Word文档(以及其他文件)作为blobs存储在SQL+Server数据库中。您可以阅读有关此here的更多信息。|3624629|entityMap|0|LINK|mutability|MUTABLE|url|http://research.microsoft.com/apps/pubs/default.aspx?id=64525|1|http://blogs.technet.com/josebda/archive/2007/10/25/the-legend-of-the-single-multi-terabyte-replicating-sharepoint-database.aspx^0|0|2C|A|0|0|20|4|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Keeping your data in the database will make managing the date much easier. You won't have to make sure the data in the database is in sync with the data (file paths) on the filesystem.

Having said that, it is important to realize there might be a performance hit when storing large blobs in the database. Fortunately, there has been some research done in this area to investigate possible scenarios. I would recommend you take a look at <a href="http://research.microsoft.com/apps/pubs/default.aspx?id=64525" rel="nofollow noreferrer">this paper</a> by Microsoft Research on the subject. Hope that helps.

Furthermore, I should mention that Microsoft SharePoint stores its Word documents (as well as other files) in SQL Server databases as blobs. You can read more about this <a href="http://blogs.technet.com/josebda/archive/2007/10/25/the-legend-of-the-single-multi-terabyte-replicating-sharepoint-database.aspx" rel="nofollow noreferrer">here</a>.

blocks|key|1308460|text|没有什么是你不能同时做到的--解析文档并将重要的元信息(如联系人信息、常用单词等)存储到索引列中，存储文档的路径。这就是我为高可用性(高达2100万次/月)+db所做的，但我们提供的是媒体文件，但文件大小和主体大致相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308461|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|$]]

There's nothing to say you can't do both - parse the doc &amp; store important meta info (such as contact info, frequently used words, etc) into indexed columns, store a path to the document. That is what I did for a high availability (upto 21M impressions/month) db, but we were serving media files, but the file size &amp; principal is about the same.

blocks|key|5092796|text|您可以尝试将文档文件存储在单独的数据库中，并使用简单恢复模型。然后，您可以轻松地备份文档数据库，而不必担心备份的大小不断膨胀。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5092797|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|$]]

You could try storing the document files in a separate database and use the Simple Recovery Model. Then you can easily back up the documents database without worrying about your backups ballooning in size.

blocks|key|1250416|text|我有两个在文件夹中存储文件的系统-当我们在一个文件夹中存储大约20K个文件时，这两个系统的伸缩性都很差。可以通过使用子文件夹(例如2008-01,2008-02+)来解决，但正如其他人所说，您有同步问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1250417|数据库允许您归档/删除旧简历，并且不会出现同步问题。您可以在存储/检索时压缩/解压缩文本，只要不想全文搜索数据即可。假设一个10-20K的文件，你可以压缩到1-2K。没那么大。|1250418|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've had two systems that stored files in folders - both scaled poorly when we got to about 20K files in a folder. Can be solved by using subfolders (2008-01, 2008-02 for example) but as said by others, you have synching issues.

Database allows you to archive/delete old resumes and no synching problems. You can compress/uncompress the text when storing/retrieving as long as you don't want to full text search the data. Assuming a 10-20K file, you could compress to 1-2K probably. Not that big.

blocks|key|1256341|text|我负责一些管理TB级图像的应用程序。我认为这个应用程序的相似之处在于它存储的文件相对于典型的数据库行相对较大。我们发现在数据库中存储文件路径是最好的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1256342|有几个问题：|1256343|1256344|数据库存储通常比文件系统存储更昂贵。|unordered-list-item|1256345|您可以使用标准的现成web服务器等加速/分发文件系统访问，无需特殊的编码或处理即可访问文件系统中的映像。|1256346|1256347|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|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|$]]

I'm in charge of some applications that manage many TB of images. I think this application is similar in that it's storing files relatively large to typical database rows. We've found that storing file paths in the database to be best.

There are a couple of issues:

<ul>
<li>database storage is usually more expensive than file system storage.</li>
<li>you can accelerate/distribute file system access with standard off the shelf products.</li>
<li>things like web servers, etc, need no special coding or processing to access images in the file system.</li>
</ul>

blocks|key|3624819|text|我建议将其存储在数据库中，以便将所有内容保存在一起。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3624820|在数据库中存储时需要考虑的另一点是，SQL数据库可以由多个文件组成。我建议在这个数据库上创建第二个文件(.ndf)，其中包含包含BLOB数据的表。|3624821|这提供了一些关键的好处，因为它可以(1)在单独的磁盘阵列上运行，如果不断增加的需求需要它的话。(2)可单独备份和恢复。(3)不会使您的主OLTP数据库文件膨胀。|3624822|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I recommend storing it in the database to keep things together.

One additional point to consider when storing in the the database is that a SQL database can be comprised of multiple files. What I would advise is to create A second file (.ndf) on this database that houses the tables that contain BLOB data.

This provides some key benefits in that it can (1) be run on a separate disk array if increased demand ever calls for it. (2) can be backed up and restored separately. (3) will not bloat your main OLTP database file.

blocks|key|1308636|text|我倾向于使用最好的工具来完成每项工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1308637|1308638|用于存储和查询数据的最佳数据库类型是关系数据库。|unordered-list-item|1308639|用于管理文件的最佳数据库是文件系统。|1308640|1308641|使用文件系统将允许您使用正确的工具来管理文件:您可以使用操作系统的压缩功能，使用增量备份工具等，而不会使用有时可能包含大图像的结构不佳的Word文档来膨胀您的数据库。|1308642|随着文件数量的增加，从文件系统的角度来看，这个问题很容易解决:将文件存储在相对路径目录中，以便您可以控制每个目录的文件数量(例如，创建每周文件夹或在文件数量超过一定限制时创建新文件夹)。|1308643|然后，您只需要将文件的相对路径保留在数据库中。|1308644|我还会在提交时规范化文件名，以保持它们的一致性，如20090219-001.doc。|offset|length|style|CODE|1308645|正如其他人所建议的，您可以解析doc文件以提取纯文本信息，并将其存储在数据库中，以获得文本搜索的好处。|1308646|entityMap^0|0|0|0|0|0|0|0|0|P|G|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|11|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|16|8|@$Q|17|R|18|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

I'd go with using the best tool for each job:

<ul>
<li>the best database type for storing and querying data is a relational database.</li>
<li>the best database for managing files is the file system.</li>
</ul>

Using the filesystem will allow you to use the right tools for managing files: you can use the OS's compression features, use incremental backups tools, etc and not bloat your database with sometimes poorly constructed Word Documents that may contain large images.

As the number of files gets large, the problem is easy to solve from the point of view of the filesystem: store the files into relative path directories so you can keep the number of file per directory under control (for instance, creating a weekly folder or creating a new folder when the file count is over a certain limit). 
Then you only need to keep the relative path of the file in the database. 

I would also normalise the filenames at the time of submission to keep them consistent, like <code>20090219-001.doc</code>.

As other suggested, you could parse the doc file to extract the pure textual information and store it in the database to get the benefits of text search.

I'm working on job site (using asp.net 3.5) in which a user can upload one or more resumes.
Database is sql server 2005.
Whats the recommendation regarding storage of these documents?
Shall i store it as a blob in the database or just store the path in database and keep the document in the physical folder?
Can someone please mention the pros and cons of each wrt performance and scalability?

Thanks!

Storing word documents

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

我正在工作的求职网站(使用asp.net 3.5)，其中用户可以上传一份或多份简历。数据库为sql server 2005。关于存储这些文档的建议是什么？我应该将其作为blob存储在数据库中，还是只将路径存储在数据库中并将文档保留在物理文件夹中？有人能提一下每个wrt性能和可伸缩性的优缺点吗？谢谢!

问存储word文档
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问存储word文档EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问存储word文档
EN