Fresh Content on SharePointJoel.com SharePoint Ads
Subscribe in a reader
Thanks to Brad and Arun...
By default in SPS 2003 you created site collections when creating sites. In MOSS 2007 you get sub sites listed under the site collection, it's great for navigation and seamless integration. Even with navigation you can add sites that are outside of the portal, so don't let this stop you from creating site collections allowing you to better manage the sites in different content databases. It is simply default, not required.
To configure your site directory to create site collections instead of sub sites...
Go to the top level site collection, site settings -> site directory settings -> last checkbox.
As well you can require meta data for sites that are created and enforce listings of sites that are created. These settings can be managed in the central admin as well.
If you create child site collections instead of child sites, won't the navigation change Considerably? It seems site collections each maintain their own navigation map where child sites know their parent.
Joel Reply:
True. There are more reasons to consider site collections. My biggest one is the ability to move them into separate databases, true ownership at a site collection level, and quotas and storage management. With all these "management" features at the site collection level, I am cautious about encouraging a TON of subsites.
Hi,
Any idea why the "Create new site collections from Site Directory" option would be consistently grayed out?
If you see this greyed out it is because it is not enabled at the farm or web app level. There is configuration at the web app for "site directory settings"
Something that's tough to find any information on is Site Collection sizing. Let me offer up my thoughts
So if I am following you correctly, you are suggesting that instead of creating sub-site you should create a site collection and then modify the navigation manually if you want to split up the database files. I am still unclear why you would have to change the directory settings.
Thanks
Hikmer,
By default if you change nothing all sites would go into a single content database, would have no quotas, and no real owners, no usage reports, no storage reports. Site collections are powerful. I wouldn't dismiss them just because you get the navigational benefit. The navigation is extensible and you can add external links.
By changing the site directory to create site collections, you are providing the ability to create a new unit which has quota, ownership, life cycle, and the ability to be put in a separate database.
You can backup a (sub) site and restore it as a site collection which is where I was going with the stsadm -o import; -o export post.
What about permissions, can a Site Collection inherit the permissions on the Parent Portal?
PingBack from http://www.21apps.co.uk/sharepoint/site-collection-sizing-a-pragmatic-view/
What kind of irritates me is that in order to do as you say here you have to enable self service site creation, otherwise the referenced checkbox is grayed out.
I guess what I'm really looking for is a way to list site collections in the site directory automatically. More manual work I guess.
Currently when you try to add a site directory connection in a site collection you're squashed back.
If you want a listing of all the site collections on a "landing page" that is security trimmed, how would you do it?
From the Site Directory why can you only use Site Categories when creating Site Collections from the Index server itself. When logging in from the WFE's I don't get the options to force new Site Collections into the Site Categories. I have been searching and can't find a reason why. Any suggestions?
"You can backup a (sub) site and restore it as a site collection which is where I was going with the stsadm -o import; -o export post."
Hi Joel, how do you manage this? It's my understanding that a sub site cannot be promoted to a site collection.
The import or restore commands provided by Stsadm will create it as a subsite when the site collection's root URL is passed as a parameter.
I notice that Gary LaPointe has written a custom Stsadm to perform this function but it is (or at least was) using an unsupported method and seems to cause real problems in some cases.
As a result of this MOSS limitation I have recrated our whole farm's structure and dedicated databases to each top level site.
If you have a solution to this failing then I would love to hear about it.
I am not able to see Site Directory template under Publsihing site. Am I missing something?
I have a client who has over 1200 Sharepoint sites from which he needs to collect reporting data. Pulling the reports we need from one site is very easy. I could even handle a few more. But 1200? No way!
How do I confgure MOSS 2007 or WSS 3.0 to pull one report which breaks down all the data from the 1200 sites?
The reports I need most include:
- A consolidated Site Summary Report
- A consolidated report about problems
- A consolidated Usage Summary Report
Thanks,