Sharepoint High-Level Question

Question

0.00/5 (No votes)

See more:

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

Posted 3-Nov-11 0:44am

Dave Kerr

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jim lahey · Accepted Answer · 2011-11-03T02:15:00

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.

Not Active · Accepted Answer · 2011-11-03T02:26:00

Solution 2

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.

Posted 3-Nov-11 2:26am

Not Active

Comments

Dave Kerr 3-Nov-11 8:44am

Thanks for this idea, I will look into creating content types for the assets for the customers and then a view for each customer, thanks for the feedback :)

[no name] 3-Nov-11 8:55am

You may not need a view for each customer. Not knowing your implementation, it may be possible to have one view that is dynamically filtered based on login.