Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Sharepoint Database Size

  Asked By: Charmaine    Date: Feb 11    Category: Sharepoint    Views: 1517

We are currently desinging a portal server implementation with the
following attributes:

5000 Users
500 GB of Data
500.000 Documentversions

We are considering a medium server farm configuration with a sql
server 2005 cluster (2 machines).

All documents should be stored in one portal server implementation.
i.e. one site collection. We are not planing to use wss.

A friend of mine is operating sharpoint in a similar enviromnet and
claims that a site collection should not store more than 10GB of data.
Can anyone confirm this?



7 Answers Found

Answer #1    Answered By: Christop Mcfadden     Answered On: Feb 11

Are you planning to use Portal server  or WSS? Your requirements are somewhat on the vague side.

In terms of SQL server, I believe that the max that you can store in each database  is 50 gb. You would probably want to be sure that you split up your site collections into separate content databases when you're initially setting them up.

Answer #2    Answered By: Gopal Jamakhandi     Answered On: Feb 11

we plan to use only portal  server 2003. no wss at this stage.
we would like to have all content in one portal as this would make
navigation more transparent for users.
the portal would only be used for dms functions.
we would have a hierachie depth of aprox. 12-15 areas.

where does a database  size limit come from? i would have expected
that it didn't matter how much data you stored in your database..

Answer #3    Answered By: Chantal Rosa     Answered On: Feb 11

I wouldn't say that there is a hard limitation regarding DB size  in SPS 2003. In STS I believe the store was using an exchange JET store which had a limitation of 16GB.

Regarding DB sizes for SPS 2003, I would recommend splitting up content databases to improve backup/restore times.

Answer #4    Answered By: Kyla Eckert     Answered On: Feb 11

My content database  is 75GB, so I don't know if the limitation spoke
of here is correct.

Answer #5    Answered By: Damon Garner     Answered On: Feb 11

SharePoint (whether SPS or WSS) stores information in the SQL server  db. SQL server has a limit, that's where your limitation comes from.

Answer #6    Answered By: Alexis Ellis     Answered On: Feb 11

The numbers vary but a rule of thumb is no more than 50GB per content database  for recoverability concerns.

Why are you going to put 500 GB of data in portal? Is there an aversion to using WSS for some reason?

Answer #7    Answered By: Percy Beach     Answered On: Feb 11

AvePoint and other tools have the same backup and recovery limitations as the built in tools in terms of breaking things down into reasonable chunks.

There’s a pretty good consensus that large numbers of documents don’t belong in a portal.

As for user acceptance, a well customized WSS site will get better user acceptance than a portal  every time.

Didn't find what you were looking for? Find more on Sharepoint Database Size Or get search suggestion and latest updates.