Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Difference between sites created in Sharepoint and site collections

  Asked By: Ciera    Date: Nov 21    Category: Sharepoint    Views: 4485

I'm wondering if anyonw can help me. I'm new to Sharepoint and trying
to put together my first system and I'm getting confused between sites
(site collections) created in central administrator and sites created
from within the collaboration portal.

Can anyone explain the differences between these for me and why you
would want to do it one way rather than the other ?

I notice that if you set up a site collection you can back it up using
the STSADM tool - is this possible if you set the site up from the site
tab in the portal ? I can also see that if you set a site up from
within the sites tab then the link is securoity trimmed in the sites
list but if you add a site collection from Admin then you have to add a
manual link and this is not trimmed - I also didnt know whether the
links would then work with Alternative Access Names etc. Also, was
thinking of holding the data for each of these top level sites under
the portal in their own SQL databases for maintenance and support
reasons and this doesnt seem possible if you create the site from the
sites tab - it seems to create these sites as pages rather than site
collections (they dont appear under the list of ite collections in
central admin).

I was just wondering what everyone else does to create these first
sites below the portal or if anyone knows of any best practice for how
to do this or can explain what these differences are and have any
advice for what I should be doing.

I hope you guys can help me out as this is really confusing.

I can't wait to hear from you.



5 Answers Found

Answer #1    Answered By: Christian Waters     Answered On: Nov 21

The primary difference  is a site created  from the site  Directory, by
default, is a sub-site of the Site Directory Sub-site. What you then
have is a 3rd level  sub-site of the portal  root.

You can enable self service site management for the portal's web
application from central  administration. After you do this, you can then
browse to the Portal's site actions, site settings, site directory
settings, and change the default behavior to create  Site Collections
from the portal, instead of a 3rd level sub-site.

Answer #2    Answered By: Virendar Bahudur     Answered On: Nov 21

That sounds like I can have the best of both worlds !

Answer #3    Answered By: Alisha Itagi     Answered On: Nov 21

Have you used the stsadm.exe command line? There are several commands
only available there. Unless I am building a site  which will only be
used for a specific time & then deleted, I always use stsadm  to create
them, due to the extra flexibility. My 2cents at least.

Answer #4    Answered By: Elisabeth Walsh     Answered On: Nov 21

I can try looking at the stsadm  command - maybe that will help  but I
am new to this so I may have to ask for some assistance if that is OK.

I followed your advice Ben and it seems that this does create  a new
site colection for me but when I go into central  admin and my
application and look at the number of sites  in my content database
the number is not increasing.

Do you know why that is please ?

Answer #5    Answered By: Caleb Gordon     Answered On: Nov 21

Additionally, in terms of the SPS03 realm of things, if you didn't add  it
using the portal, you didn't automatically have a link back  to the portal
connection (/layouts/1033/portal.aspx). Other than that, just the ability
to set  whether or not the team site  was searched as a part of non-portal
content - which of course you could go in and manually setup...