共享点高级问题 [英] Sharepoint High-Level Question

问题描述

大家好，

我正在与Sharepoint一起解决一个概念性问题.如果我使用Sharepoint管理客户列表，那么如何为每个客户设置资产库.我希望每个客户都有一套资产，以及一个日历和一个潜在的文档库.

我正在寻找一种解决方案，该解决方案最初可以处理约25万个客户，但是可以向上扩展，因此我怀疑每个客户的子站点都将是高性能的.我是SharePoint的新手，也不知道如何为每个客户设置列表(或通常来说，保存列表的列表).这似乎是一个愚蠢的问题，但是任何帮助都会令人感激不已！

预先感谢，

Dave

Hi Guys,

I''m struggling with a conceptual issue with Sharepoint. If I use Sharepoint to manage a list of customers, how do I set up an asset library PER customer. I want each customer to have a set of assets, as well as a calendar and potentially a document library.

I''m looking at a solution that will handle initially about 250 thousand customers, but scale upwards, so I doubt a sub-site per customer will be performant. I''m new to sharepoint and don''t know how to set up lists per customers (or in general, lists that hold lists). This may seem like a stupid question but any help would be incredibly grateful!

Thanks in advance,

Dave

推荐答案

从您提到的每个客户的子站点来看，这听起来很合适，但是在引用数字时考虑扩展性是正确的.

您需要在Technet上参考Microsoft的容量规划文档:

http://technet.microsoft.com/en-us/library/cc261700.aspx [ ^ ]

特别是下一个链接应该为您提供有关容量和扩展性的明确答案:

http://technet.microsoft.com/en-us/library/cc262787.aspx [ ^ ]

您可以采取多种措施来最大化SharePoint安装的容量和性能.

您绝对可以看到的一件事是，以这样的方式配置网站集:每个网站集在SQL Server中都有一个专用的内容数据库，并且可能将您的客户群分布在多个单独的网站集上，因此您不会遇到容量限制.其他选项包括SharePoint数据库的磁盘优化以及将SQL Server配置为用于远程Blob存储以将二进制内容存储在文件系统而不是数据库中:

http://technet.microsoft.com/en-us/library/ee663474.aspx [ ^ ]

希望这对您有所帮助.

From what you''ve mentioned a sub-site per customer sounds suitable, but you are correct in considering scalability with the figures you''ve quoted.

You need to refer to Microsoft''s capacity planning documentation on Technet:

http://technet.microsoft.com/en-us/library/cc261700.aspx[^]

The next link in particular should give you some definite answers regarding capacity and scaling:

http://technet.microsoft.com/en-us/library/cc262787.aspx[^]

There''s a whole range of things you can do to maximise the capacity and performance of your SharePoint installation.

One thing you can definitely look at is provisioning the Site Collections in such a way that each Site Collection has a dedicated content database in SQL Server, and maybe spanning your customer base over a number of separate site collections so you don''t run into capacity limitations. Other options include disk optimization of the SharePoint databases and configuring SQL Server for Remote Blob Storage to store binary content in the file system and not the database:

http://technet.microsoft.com/en-us/library/ee663474.aspx[^]

Hope this helps.

尽管SharePoint可以处理250,000多个子站点，每个客户都有一个子站点，但是您当然需要硬件来支持它.可伸缩性绝对是一个问题.

尽管根据您的使用情况，使用带有标识客户的字段来创建内容类型可能更合适.一个图书馆可以处理数百万个项目，并且可以创建视图以供客户过滤.这样会更高效，更可扩展.

Although SharePoint can handle 250,000+ sub sites, one for each of your customers, you would of course need the hardware to support it. Scalibility would defiantly be an issue.

Depending on your usage though it may be more appropriate to create contenttypes with a field identifying the customer. One library can handle millions of items and views can be created to filtered by the customer. This would be more performant and more scalable.

这篇关于共享点高级问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！