Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

How deep in the hierarchy can a nested sub-site be created?

  Asked By: Nilay    Date: Sep 13    Category: MOSS    Views: 2361

I am trying to establish guidlines in our organization with regard to
sharepoint. Now, I understand that the best practice is to create multiple
site-collections as opposed to sub-sites, however, we have just a single
site-collection which is being used primarily for internal collaboration. So
question is, how deep in the hierarchy can I allow one to create a sub-site?

I don't want to have nested sub-sites inside nested sub-sites. I have looked at
all the SharePoint 2007 hard limits, but could not find any reference to optimal
depth at which a sub-site can be created.

Note: We are using Windows SharePoint Services 3.0

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Mayur Mandal     Answered On: Sep 13

There are no hard limits per se, but the limitation you are most likely
to hit involves URL length. There are a variety of limits on URLs
ranging between 160 and 255 characters in various parts of both
SharePoint and the Office client integration.

 
Answer #2    Answered By: Deana Lowery     Answered On: Sep 13

Consider the Site Collection as a Server and create  multiple Sites
(sub-sites.) Don't make the sub-sites  nest. Make multiple "Sites."

 
Answer #3    Answered By: Felecia Goff     Answered On: Sep 13

"Best practice" is a relative term.

What is the purpose of nesting a site? If it's not so that you can inherit
permissions, then it's probably not worth it. Rarely is it advisable (and
never necessary) to create  a site structure solely for the purpose of
maintaining navigational elements. You can slice and dice the global nav
and Quick Launch any way you like, so don't let those constrain your
hierarchy.

 
Answer #4    Answered By: David Scott     Answered On: Sep 13

The purpose of the sub-site  was to maintain some confidential information for a
certain period of time before it can be made public (this is for auditing and
auditing guys do not want to share which agency they are auditing). So it has a
different audience than the parent site (in this case it is general auditing
site with references to policies and procedures).

 




Tagged: