Hello, we're currently planning to use sharepoint for all corporate documents. our intention (at the moment, please correct me if there's something wrong or unhandy..) is to use one document library with several content types (add. columns for each content type). At the moment we have for the complete company one web-application in one content database (which's at the moment about 5 gb big), containing about 40-50 workspaces.. I guess now, when we will add 1500 to 2500 documents into that library this will increase the database and slow it down, also the impact on errors would increase a lot.. So my question now: is there a way to create a second content database for the web application (and I'd like to stay within the same web application, to benefit from relationship, etc.) and place the new document library in that database? looking forward for any proposals, thanks for the feeback!!

Hello, The recommended limit for content databases per Web application is 100. This is not a hard limit, just a best practices recommendation. Each site collection in your Web app will store its content in a content database. You can have multiple site collections using the same content db (50,000 is the recommended limit), but you cannot have a site collection saving to more than one content db. 5 GB of content is nothing to worry about at the momemt, but keep in mind that you will want to monitor the size of your content db's. Depending on who you talk to, recommended limits (not actual hard limits) will be to keep your content db's below anywhere from 75-100 GB. This is for multiple reasons: backup/restore time for large db's, complicated timer jobs that run daily can lock your db if it is too large, etc...Another thing to consider is using multiple document libraries rather than trying to put everything into one library. Is there any particular reason for using only one library?Chris Caravajal MCTS SharePoint Help

Hi, Limits on storing content in the same library - The maximum recommended size of a library is 10,000,000 documents.- To apply unique document management settings to content, such as required checkouts or versioning, the content must be stored in a separate library.- If multiple content types are used in a library and each content type has one or more columns of metadata that only apply to that content type, views can become confusing. To alleviate this, you can associate each content type with a separate library.- The performance of views of content degrades when the number of items viewed exceeds 2,000 items. Remedies for this limitation are to organize the content in the library into folders each containing 2,000 or fewer items, or to create views that take advantage of indexed columns to return sets of 2,000 or fewer items (see below for a discussion of using indexed columns in views).http://technet.microsoft.com/en-us/library/cc263028.aspx#section4Best Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.

Hi, as of now first thank you for the answers. The reason for one database is/was to have each document into one database, but viewed from the library-size it has its charme to use a dedicated library for each content type... anyhow, my origin question was if it possible to attach a second database and force new content o be created in this database...

Hi,Yes you canPlease check this http://blogs.technet.com/corybu/archive/2007/06/21/sharepoint-site-migration-and-balancing-growth.aspxBest Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.

Hi, I was just testing and (sadly) my complete intranet is one website... for testing I created a second website in the database, but unfortunately now I don't have the navigation included... not very happy with this..