Re: DB architecture for WSS sites on SPS server

Steve,

Thanks for the clarification and information. It all seems to make sense to
me now. As we are not a very big SPS / WSS user, the 25GB limit shouldn't be
an issue for us. We've only got about 10 WSS sites on our SPS now at just
under 1GB of content.

We had purchased the Veritas SharePoint backup agent to plug into our
Veritas 10d infrastructure, but were dissapointed to see that it didn't offer
a document-level restore. Looks like we'll have to investigate some
third-party solutions for our backup and restore.

I just got the new Windows IT Pro magazine which did give a pretty go review
of AvePoint as a solution. Commvault's Galaxy Backup & Restore got Editor's
Choice and we may look in that direction also.

Once again, thanks for the help and information.
--
Sandy Wood
Orange County District Attorney


"Steve Smith" wrote:

By design it is a single database but practically it is very bad. If you
plan on going anywhere over 25GB of data and up to a max. of 50GB it is
recommended to create seperate databases for the content. This can be
achieved either by creating stand alone site collection which have their own
databases as you mentioned or as Joe mentioned you can create additional
content databases in central admin for the virtual server. Note however that
only Top level team sites are distributed amongst the databases and also you
need to limit the amount of sites in the existing content database which
will say up to 15000 sites are allowed. So if you have 200 sites make the
max 200 sites and then create a new content database and all new top level
team sites will go there.
As you are also correct this will affect backup and restore - you may want
to look at products like avepoint to also help with that granular level of
sites and libraries.

Steve Smith
www.combined-knowledge.com


"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message
news:849420E9-A67B-40B5-9898-377518A89BF7@xxxxxxxxxxxxxxxx
Thanks for the info. I'm just concerned that if I need to restore a
specific
WSS site, for example, I'll need to restore all the sites that are in that
same content database. I suppose that's the way it is, but it does seem
unusual. I suppose I could manually create a new virtual server and then
extend it into a WSS site. That would keep the databases apart.
--
Sandy Wood
Orange County District Attorney


"Joe" wrote:

Yes it is by design.

In Sharepoint Central Administration it is possible for you to create
another content DB that will be used to store data for any new site
collections.

Joe





.

Relevant Pages

  • Re: Copying WSS to another Server
    ... the data in sync I back the SQL databases up and restore them to the replica ... It already has WSS installed. ... > on one server and copy it to another for dev/test purposes, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Copying WSS to another Server
    ... I do not restore the Config databases, ... It already has WSS installed. ... Go to your virtual server settings and manage Content Databases. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Moving SQL Server 2000 from NT4.0 to Windows 2003
    ... Detach your existing user databases, ... user databases (or RESTORE) to the new server. ... > Hey Steve, ... Windows 2003 will not allow SQL Server SP less than 3. ...
    (microsoft.public.sqlserver.server)
  • Re: Restore a WSS server with SQL databases ONLY?
    ... WSS Server if I only have backups of the databases?" ... > 4) Restore ContentDBs to SQL. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Copying WSS to another Server
    ... The WSS Admin guide has more ... >I do not restore the Config databases, ... It already has WSS installed. ...
    (microsoft.public.sharepoint.windowsservices)