saleemz
asked on
SharePoint Site Creation Best Practices
Hi
We are in the process of deploying SharePoint. Can someone at EE help us with the guiding us in the right direction. One of the questions we have is what are the best practices for setting sharepoint sites Should we create a site for each area eg Finace, Corporate, Admin, HR, Operations or should we have everything in one. I mean when is OK to create separate site and when it is not
PS: We are using SharePoint Standard 2010 (NOT SPF)
Thanks
Kashif
We are in the process of deploying SharePoint. Can someone at EE help us with the guiding us in the right direction. One of the questions we have is what are the best practices for setting sharepoint sites Should we create a site for each area eg Finace, Corporate, Admin, HR, Operations or should we have everything in one. I mean when is OK to create separate site and when it is not
PS: We are using SharePoint Standard 2010 (NOT SPF)
Thanks
Kashif
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Some considerations...
The Content Query Web Part can only query within a site collection. So for example, if you want to be able to roll-up information across departments using the CQWP, you should make them sites in the same site collection.
Site Collections have their own security groups, and don't share those SharePoint groups with other site collections. So if you generally need to isolate security, using separate site collections is the way to go. If you need to share the security groups, you may consider sites within the same site collection.
Sites share the same content database as the site collection they are located in. So if you need different SLA's, you may want to consider different content databases - meaning different site collections.
There are other considerations, but those are a few to get you thinking...
The Content Query Web Part can only query within a site collection. So for example, if you want to be able to roll-up information across departments using the CQWP, you should make them sites in the same site collection.
Site Collections have their own security groups, and don't share those SharePoint groups with other site collections. So if you generally need to isolate security, using separate site collections is the way to go. If you need to share the security groups, you may consider sites within the same site collection.
Sites share the same content database as the site collection they are located in. So if you need different SLA's, you may want to consider different content databases - meaning different site collections.
There are other considerations, but those are a few to get you thinking...
ASKER
Hi Thanks for the comments Much appreciated I found this related article which is very useful http://technet.microsoft.com/en-us/library/cc262410(printer).aspx
ASKER
Hi All
I found this article useful related to this question.
http://technet.microsoft.com/en-us/library/cc262410(printer).aspx
Kashif
I found this article useful related to this question.
http://technet.microsoft.com/en-us/library/cc262410(printer).aspx
Kashif
It all depends on your requirements. TechNet has some great resorces, as Teylyn noted.