Tag Info

Hot answers tagged

20

I would like to take the opportunity to pimp a few of the posts on my own blog: Site Topology Planning Part 1 Site Topology Planning Part 2 Environments can vary quite a bit in the number of site collections they will have or how deep the site hierarchies will go. The amount of content in those site collections also can very. I once had a sub-site that ...


14

My response echo's a little of what Mike said... a lot of site collections stay pretty small, in which case it is much more efficient to keep them in a single content database so that there's not as much overhead (more about the number of objects in the instance than a performance perspective) in SQL Server associated with them from a database perspective. ...


14

If all you want is a list of all site collections in the farm, all you have to do is open a PowerShell window, load the SharePoint snapin if you haven't (Add-PSSnapin Microsoft.SharePoint.PowerShell), and type Get-SPSite. If you want to return the list of site collections for a specific web application, the easiest way is to just pipe it as ...


13

I think that you could look at the managed paths Open Sharepoint Central Administration -> Application Managment -> Manage web applications Select your web application Click Managed Paths button on the ribbon You will see that there are at least two path: Root (Explicit inclusion) sites (Wildcard inclusion) Explicit inclusion means that you can ...


10

// root site – eg. Web App url string rootSiteCollectionURL = SPContext.Current.Web.Site.WebApplication.Sites[0].Url; // site collection url string SiteCollectionURL = SPContext.Current.Web.Site.Url;


9

For now, SharePoint 2010 does not support event for site collection adding or added.So it is not possible to do it programmatically Yes, You can plugin your feature to the site definition used for the site collection by "Feature Stapling". You can define a feature at scope of Web application. It will automatically activate the stapled feature(which is your ...


8

Get-SPWebApplication xxx | Get-SPSite -Limit ALL | % {Enable-SPFeature "xxx" -Url $_.Url}


8

What you're looking for is the host named site collection, which enables you to assign a unique DNS name to site collections. Or alternatively create an AAM for existing Site collection to achieve it. For example, you can address them as http://hr.mycompany.com or http://sales.mycompany.com. The sample PowerShell code creates a new web application listing ...


8

The text is due to confusion SharePoint creates by having three different groups which when you create a site collection start out having the same persons, but are in fact different. The three groups are: Site Collection Owners Are controlled via `Central Administration | Application Management | Change site collection administrators' Receive email about ...


8

You're within the limitations of SharePoint (http://technet.microsoft.com/en-us/library/cc262787.aspx) in either scenario, which is good. Some of my thoughts As far as performance, I don't think you'll see much in way of improvement going from one DB to multiple DBs, unless you can move the DB files to different disk arrays. 100GB is a reasonable size for ...


7

The Publishing Features need to be active on the site collection for the web part to appear. It can be activated from the Site Settings, Site collection features screen.


7

Yes, it's possible. The (probably) easiest way is to use feature stapling. Then you can say that all new instances of e.g. STS#0 (Team site), should activate this feature. <FeatureSiteTemplateAssociation Id="b8f334a0-1ffe-420d-b6e2-54a9faa6ba95" TemplateName="STS#0" />


7

Go to "Site Settings -> Users and Permissions -> People and groups" Click on the "Settings" menu and "List Settings" Scroll to the bottom of the page and click on the view that you want to export. Copy the url and in particular the List and View IDs ...


6

As well as the other good information already provided by Mike and John there is also the flexibiliy you can gain from using multiple databases when you rely on the native SQL Server/SharePoint admin tools for managing your environments. For a starter it may make your content deployment/migration and backup/restore scenarios easier (from a database ...


6

You can define another navigation provider that pulls the data from a different source. Typically I use a SharePoint list, but you could use an XML file, database, or whatever makes the most sense for your requirements. The menu control placed on the MasterPage can either have the data source repointed, or you could decide to put a second control on the ...


6

Using only the Client Object Model you cannot access another site collection. You can however connect to the web services directly using a variety of methods/libraries such as jQuery. When crossing the site collection boundary, I'll mix and match the two approaches as needed.


6

If you want an event receiver on anything, then it's best to attach it to the content type Item (0x01) Example: CharlieDigital: Programmatically Adding an Event Receiver to a Content Type


6

SPContentDatabase.ForceDeleteSite http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spcontentdatabase.forcedeletesite.aspx use this method to force a delete: SPWebApplication spWebApplication = SPWebApplication.Lookup(new Uri("http://mywebapplication")); // insert the webapplication ...


5

Try creating a new site collection (team site) under the same web app. Perform the same security configuration with the groups and all that. Do you experience the same behaviour? Also, do you have a custom master page? If so, firstly ensure it is in a published state. Are there any custom controls on it that try to access protected resources (i.e. a control ...


5

Many points can be taken in consideration while choosing web application or site collection. Some important ones are: 1) Web application provides isolation. If your web application uses a unique application pool in IIS, the isolation is at Process level. If your web application uses a shared application pool in IIS, the isolation is at Application Domain ...


5

Try SPContext.Current.Site.RootWeb.RootFolder.WelcomePage


5

Setup Audit Logging in SharePoint 2010 to accomplish this. Visit this blog to see how this is accomplished. Check out the office site to see what all features are captured in Audit logging.


5

Can't test it myself but it wouldbe something like this: ######################## Start Variables ######################## $LoginName = "domain\login" $siteURL = "http://SharePointSiteURL" #URL to any site in the web application. ######################## End Variables ######################## Clear-Host $siteCount = 0 ...


5

You can use SPContext.Current.Site.HostName property to get the host name? Normally you can use SPContext.Current.Site.Url to return the Url of the root website in the site collection for the current web request. If you want the context of the current web site then use SPContext.Current.Web.Url.


5

Check your web application user policy and see if builtin\administrators have full control.


5

Try this for the first link as it is intended to address exactly what you are seeing, though certain controls do not expand the value. <CustomAction Id="script1" Location="ScriptLink" ScriptSrc="~SiteCollection/Style%20Library/mySolution/custom1.js" /> As to whether it should be in _layouts or Style Library is a debate that has raged since the ...


5

Object cache: What Object cache does is stores metadata about SharePoint Server objects (like SPWeb, SPSite, SPList, etc.) on the WFEs. When a page is rendered, if there is data that needs to be retrieved through these objects, the SQL Server will not be hit. Features of SharePoint that uses Object cache are publishing, content query web part, navigation, ...


5

Here are two ways to tell the robots to not crawl your site: Adding robots.txt with the following content in the root folder with SharePoint Designer (All Items in SPD) User-agent: * Disallow: / Adding meta tag in your master page's Head section as below should prevent the robots from crowling you site. <meta name="robots" content="noindex" > ...


5

There are a couple of things you can try... such as 1. Get-SPDeletedSite & Remove-SPDeletedSite You may already have restored this site before. In that process you also deleted the site first (automatically), which you can find running the command... >Get-SPDeletedSite You'll see the site (or sites) listed, like this: WebApplicationId : ...


5

$site = Get-SPSite http://intranet.sharepoint.com/ $site.RootWeb.Author where SPWeb.Author property gets a user object that represents the user who created the website



Only top voted, non community-wiki answers of a minimum length are eligible