Go 4 Sharepoint

Search:

Welcome: Guest!

MOSS Forum

Home » Forum » MOSS

Ask a question

RSS Feeds

Moving some DB content to another database linked to a ne

Asked By: Stewart Espinoza Date: Jun 05, 2007 Category: MOSS Views: 265

I have a MOSS 2007 installation that was created by upgrading a
SPS2003 server. There are several issues with the configuration, but
I'll start with the most (potentially) confusing.

Currently everything is running on one IIS web application. I'll call
this "MainSite". What I would like to do is pull one of the largest
site collections out of the database, create a new database, and tie
it to a new IIS web application (SubSite1). Is there any way to do
that, and, if so, what type of information gets lost (such as user
permissions and document revisions)?

My eventual goal is to have the main portal on its own IIS web app
(MainSite), and each subsidiary site on its own IIS web app
(SubSite1, SubSite2, SubSiteX...) tied back to the main portal. Does
this make sense? Would I be able to create search scopes to search
the MainSite, the SubSite, and/or All Sites? Or should I just go
ahead and create new site collections for each subsidiary on the main
portal all in one IIS web app?

Tagged:moving some db content to another database linked ne

5 Answers Found

Answer #1 Answered By: Aditiya Kapale Answered On: Jun 05, 2007

Site collections cannot span multiple content databases. You could seperate out
your current top-level sites into differing content datases, but it would have
no navigational connection to the main site. Each web application is autonomous
from the other.
That being said, you could still set up search scopes so each could crawl the
other.

Answer #2 Answered By: Cristopher Gould Answered On: Jun 05, 2007

Actually it's the second option that I'd like to do.
I don't want the site collection to span multiple content databases. I
want to take a site collection and move the entire contents to a new
content database. Any ideas on how would I go about doing that in
MOSS'07 ,or even if I should? Bear in mind, I'm not the SQL person, just
the SharePoint administrator.

If anyone needs more details to clarify what I am thinking about doing,
don't hesitate to ask.

Answer #3 Answered By: Selena Glenn Answered On: Jun 05, 2007

That's easy enough to do. In order to do that, follow
these steps:

Set your current content DB max site settings to
however many sites you currently have.
(This will prevent any new sites from being added to
this content DB)

Create and attach new content DB

Set max site settings on this new Content DB to 1.

Perform a STSADM -o BACKUP ... operation

Perform a STSADM -o DELETE ... operation

Perform a STSADM -o RESTORE ... operation
(This will restore the site into the new Content DB as
it is the only DB currently accepting new sites)

Change original content DB max site settings back to
original settings.

Repeat as needed.

Answer #4 Answered By: Jonathon Palmer Answered On: Jun 05, 2007

I'll give that a try.
Last time I attempted to do a backup, I received errors when it came
time for the databases to be accessed. I've got some permissions that
are not set up as they should be, but that's something that I'll post in
a different thread.

Answer #5 Answered By: Aastha Patel Answered On: Jun 05, 2007

I did that recently using 3 farms

Farm 1 aps2003

Farm 2 update content db by using stsadm addcontentdb - this pdates the sites to
2k7 then use stsadm backup to backuo the site collections

Farm 3 moss use stsadm restore to add site collection to pristine environment

I wouldn't recommend this but if its the route you want it works

You just need to delete the old site and replace with a pointer oe find some
other way for users to know which url or farm to connect to

Didn't find what you were looking for? Find more on Moving some DB content to another database linked to a ne Or get search suggestion and latest updates.