Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Architecture Of SharePoint sites

  Asked By: Amie    Date: Jul 30    Category: Sharepoint    Views: 913

My client has locations in different cities across the country.They want the
teams in the individual location to collaborate using sharepoint and also they
want sites for their different business teams.

I have proposed that they create sites as

http://client.location1.com One web application in sharepoint

http://client.location2.com Another web allpication in sharepoint

a web application for each of their business applications.

But the client is suggesting that we should have all sites under port 80.

What are the advantages and disadvantages of having everything under port 80
that is a single site collection.
2.What is the best paractise in such situtations .Can anyone point me to
some design documents for sharepoint projects.



7 Answers Found

Answer #1    Answered By: Shashwat Takle     Answered On: Jul 30

Does anyone have an answer to this.

Answer #2    Answered By: Aastha Acharya     Answered On: Jul 30

Have you considered a hosted solution.

We offer a fully managed hosted solution at officetalk.

Answer #3    Answered By: Glenda Roth     Answered On: Jul 30

You can create  separate site  collections for each client  under a single
top-level site < http://servername:80 >. These would appear under
http://servername/sites/<site1>, http://servername/sites/<site2>, etc.

This is probably the easiet way to host multiple site collections, IMHO.

Answer #4    Answered By: Jada Clemons     Answered On: Jul 30

Too many web  applications on a single  server causes performance issues.
I know this because I work for a company who had hoped to put 300
collections per server (in farm mode). Through a ticket with MS we
confirmed this to be an issue. I don't know how many sites  you are
planning but you will see degraded performance as the number of sites
increase so I would recommend using one top level site  and then
sub-sites. If you still want to pursue multiple web applications  then
you may put them all on port  80 by adding an IP to the box for each site
or using host headers (I believe MS doesn't recommend using host headers
but I can't be sure).

Answer #5    Answered By: Brooke Lewis     Answered On: Jul 30

The issue isn't the number of site  collections. It is the number of Web
applications. In 32bit, you only have 1GB of memory available for
application pools.

With 64bit, you can have much, much more. Still, about 300 web  APPs is a
lot...Think 'http://webapp1', http://webapp2'

Whereas a site collection  would be http://webapp/sites/sitecollection1 ,
http://webapp/sites/sitecollection2. Then, you can have something like
50,000 site collections per database. Obviously, this is a software
boundary, and most hardware could not support it.

And ALWAYS use host headers, even when assigning IP addresses, if you
want to restore using the native tools. The software restores all sites
to port  80 (or whatever you chose when buiding) and can be a real pain
to restore.

Answer #6    Answered By: Talia Johns     Answered On: Jul 30

How much of a memory hit is each application  pool?

Answer #7    Answered By: Tera Callahan     Answered On: Jul 30

We have seen large intranet publishing sites  easily consume 800MB of
memory. Btw, about 1gig is the maximum recommended size (sorry, internal
discussions with msft and no technet article, yet). But, only grow app
pools that large if you *really* know what you are doing.

Didn't find what you were looking for? Find more on Architecture Of SharePoint sites Or get search suggestion and latest updates.