Limitations of SharePoint 2013 (i) WEB application and content Database

Limitations of WEB Application

SharePoint Farm supports up to 20 webapplication. This restriction has nothing to do with the application pool limit, which is for the entire farm. Microsoft recommends that the smaller the number of Web application be controlled, the better. If you want more than one site with different names, you can create a host named site collection instead of adding a new Web application.

A We application supports up to 5 zones. This is a SharePoint definition that is dead and cannot be modified.

A Web application supports a maximum of 20 Managed Path. In fact, more creation is also possible, but this will cause problems in efficiency. Because each managed path is cached on the Web Front End server.

Issues to consider before creating a Web application:

1. It's best to take a better name for the Web application and have some rules.

For example: For the company's internal office site WebApplication, can be called htpp://portal.contoso.com

For personal sites, call http://mysite.contoso.com.

For interacting with external partners, call http://partner.contoso.com

2. It is also necessary to have rules when creating content database. In general, SharePoint randomly arranges a name, followed by a string of GUIDs. It is best to modify the Web application name+[identity]. Because there may be more than one content database under a Web application, differentiate it with an identity.

This avoids the mistaken database when maintaining the database.

3. What authentication methods are supported?

For internal sites, Windows authentication is generally not allowed for external access.

4. Do you want to turn on anonymous access?

Anonymous access needs to be turned on at the Web application level, so for security reasons, sites that allow anonymous access have a separate Web application.

5. What application Service does this Web application consume?

Limitations of Content Database

1. A farm supports a maximum of 500 content Database. Adding too much content database to a Web application can lead to administrative headaches. For example, creating a site collection is slower, and if the content database is too large, it is recommended to use PowerShell commands to manage SharePoint instead of pages.

2. Content Database Size limit

For different purposes, the recommended size limits are not the same.

• Generally speaking, it is recommended not to exceed 100GB, maximum of 200GB. Because the larger the database, the more cumbersome it is to maintain. For example, in order to not affect the user's use during the day, you want to make a database backup at night, then you have to ensure that the hours of the night can be backed up.
• If you can guarantee a high level of responsiveness, fast backup mechanism, high availability and disaster recovery, a content database can reach 4TB
• For archived documents, there is no specific limit on the size of the contentdatabase. But make sure the site template is in document Center or record center. And there is a very small number of files that need to be accessed (<5%), and very few files need to be modified (<1%). Other interactive features, such as alert,workflow, that break integration permissions should not be used.

3. A content database can store 60 million item. More than that, it should be stored separately in multiple content database.

4. A content database can store up to 10,000 site collection. Can be

• 2,500 common site collections, plus 7,500 personal sites
• Or a 10,000 personal site

For more information, please visitsoftware boundaries and limits for SharePoint

Limitations of SharePoint 2013 (i) WEB application and content Database