有关创建映像存储库的问题 [英] Question about creating an image repository

问题描述

大家好！

我不知道应该去哪里，所以我暂时把它发布在普通小组，但我很乐意讨论在其他地方，如果它更合适。

I wasn't sure where this should go, so I posted it in the general group for now, but I'm happy to move the discussion somewhere else if it is more appropriate.

我有一个小程序，我已经建立了管理项目跟踪，我想有一个部分来管理图像资源。 我的问题是，它将包含成千上万的图像，我不知道如何最好地接近它。 他们所有
都很小（10 kb以下），但我不确定我是否应该将所有这些存储在SQL数据库中，或者不同的东西？

I have a small program I've built to manage project tracking and I want to have a section to manage image resources.  My problem is that it will contain hundereds of thousands of images and I'm not sure how best to approach that.  They would all be small (under 10 kb), but I wasn't sure if I should store all of this in a SQL database, or something different?

我'有点想象它有点像微软停产的Expression Media，它可以同时保存和显示大量图像。

I'm kind of envisioning it being a little like Microsoft's discontinued Expression Media, where it could hold and display a lot of images at once.

非常感谢任何想法或建议。

Any thoughts or recommendations are greatly appreciated.

谢谢！

推荐答案

您好，

有优惠和将图像存储在文件系统中与将图像存储在数据库中的缺点。一个体面和简单的概述可以是

在这里找到。请注意，使用文件流需要一些时间来配置，但这不应被视为一个缺点，只是好知道。如果存在安全问题和性能问题，那么两者很容易在本地
框中竞争，而在数据库中图像更安全，但性能可能最终成为导致正确设置SQL Server的问题。

There are advanages and disadvantages to storing images in the file system vs. storing images in the database. A decent and simple overview can be found here. Note that using file streaming takes some time to configure but that should not be seen as a disadvantage just good to know. If there are security concerns and performance concerns the two can easily compete against one and other as on a local box images are more secure in the database but performance may end up being an issue which leads to properly setting up the SQL Server.

SQL-Server与MS-Access？放下那么多图像不会考虑MS-Access。

SQL-Server vs MS-Access? Hands down with that many images would not consider MS-Access.

这篇关于有关创建映像存储库的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！