Tag Info

Hot answers tagged

8

I think SharePoint is a powerful, feature-rich, and extensible platform and can fulfill your capacity needs if DESIGNED correctly (Information Architecture, Solution Architecture, Infrastructure Architecture and Storage) You can use a web application and divide the blogs into site collections. Below are few points that may adress your concerns: ...


4

The minimum database size is a recommendation, not a stop. Check out my blog post on databases and SharePoint: http://davidlozzi.com/tag/database/. If you're looking to move above the minimum requirements, you'll need to include additional maintenance tasks, possibly improve hardware and such. SharePoint can support 4TB databases, its up to the ...


4

Here are some details about support for large databases with SP1. http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=988 Officially there is support up to 4TBs with optimization, but realistically that is difficult to support and should only be used in extreme exceptions. Technically there were no real changes made to support the additional ...


4

I would strongly recommand you get support from an architect as the questions to be answered here go beyond those expressed here: e.g. what is the total volume of data, what is the quality of the WAN connection between locations, how would you plan to secure connections, what services you want to share/consume across locations, how is your AD structured, ...


3

Basically yes, that includes everything (blob storage). You can go over that limit, but there are some very specific requirements if you do. Take a look at the requirements in these links: http://technet.microsoft.com/en-us/library/cc262787%28office.14%29.aspx#ContentDB http://technet.microsoft.com/en-us/library/hh307867%28v=office.14%29.aspx Here ...


3

The technet page RJ linked to in his comment is one that I refer customers and management to all the time. These limits are there for a reason and they mention special scenarios where these limits can be broken. For example: Content databases of up to 4 TB are supported when the following requirements are met: Disk sub-system performance of 0.25 ...


3

I found the easiest way to move/copy contacts over to a Sharepoint Contacts list. Navigate to the List in Sharepoint and click on "Connect to Outlook". Now you will have the contacts list show up in Outlook under your contacts tab. Find the folder in Public Folders where the contacts are stored and simply select all your contacts (ctrl+A), drag and drop ...


2

Take a look at HP's Sizer tool for SharePoint. The one for 2007 has long been a staple in any farm sizing exercise, and they have now made the 2010 version available. Everything will be in terms of HP-branded hardware but you can easily convert to other brands. They also have a bunch of whitepapers and guides here 70k users is a fairly big farm, I don't ...


2

These guidance posts may be helpful as scenarios can vary - 5 Best Practices to Configure Diagnostic Logging with PowerShell Commands Best practices for operational excellence Best practices for capacity management UPDATE: Usage logging databases require ongoing maintenance. You can plan on how it's going to be used by selecting the tracing variables ...


2

RBS can be used both in an archiving scenario (where we offload documents from SharePoint that are rarely used or updated) but it is also very useful for ACTIVE content that is simply being stored outside the content databases... In these "collaborative" instances, we want to make sure that the external storage location where we store the BLOBs has good ...


2

If you have a lot of data to migrate, you could look at third party tools to assist with moving data. I just tried with a public contact list here, I selected all the users, copied them, pasted them into Excel and from there, you can massage any data, and upload it to a contacts list in datasheet view.


2

3000 items in a list is no problem. SharePoint supports up to 30,000,000. See SharePoint Server 2010 capacity management: Software boundaries and limits Viewing more than 2000 at a time degradades performance.


2

The "Capacity Management" explicitly states that 2.000 is a threshold: Subsite | 2,000 per site view | Threshold The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Similarly, the All Site Content page and the Tree View Control performance will decrease significantly as the ...


2

If this is primarily a blog platform, then I would not be too worried about the storage size. The blog posts will not be that large, and unless the images are enormous they will not take up significant space. I agree with David's comments on database sizing and limits. When thinking about quotas and sizing, you will find that you will not have uniform use ...


1

Capacity Planning is what you need here. Its a whole lot easier if you plan for capacity from the start as information tends to get bigger with passing time on any Intranet. With the context of SharePoint, there can be multitude of factors that should be considered before restructuring your intranet solution design along side sizing for content databases. ...


1

There are no hard rules you can follow as they will be different in every enviroment. Topology is based on your requirements. Technet some diagrams for some basic deploment methodologies: http://technet.microsoft.com/en-us/library/cc263199.aspx You need to determine your fault tolerance requirements in combination with your performance requirements to ...


1

I seem to rememeber reading somewhere that you were not allow to publish SharePoint performence metrics. So the only place I know that has this kind on info is msdn. I referenced this page a lot for sp2007: http://technet.microsoft.com/en-us/library/cc261795(office.12).aspx And the tool: ...


1

One of the simplest techniques for this is to use ordinary SQL backups (for which your DBAs should be very familiar with). Whenever you then need to restore an item, list or site (that's not in the recycle bin) is to use the SQL backup and either mount it to a dummy farm or web application or use unattached content db approach. This does not require any ...


1

I would recommend checking out AvePoint's whitepaper on RBS, this explains the sizing in more detail and will answer your question. Dan Holme, SharePoint MVP and Chief Evangelist at AvePoint, wrote this white paper: http://www.avepoint.com/assets/pdf/sharepoint_whitepapers/Optimize_SharePoint_Storage_with_BLOB_Externalization.pdf


1

Number of Application Pools per web server Supported are 10. Limit depends on RAM allocated to web servers and workload of the farm (user base and usage characteristics – a single highly active application pool can reach 10GB or more) http://www.sharepointsharon.com/2011/08/sharepoint-2010-performance-and-capacity-limits/


1

Assuming that you assign separate Application Pool to each Web application, The recommended limit is 10. Yes, it depends on the server hardware. Regarding IIS, anyway you will be using IIS 7.x for SharePoint 2010. For details, see here : http://technet.microsoft.com/en-us/library/cc262787.aspx#Boundaries



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