• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 383
  • Last Modified:

Linking Sites to existing content DB's

We recently had a sharepoint server go down and attempted to rebuild a server using the existing config db which was a no go.  So what we decided to do is create a new server, server farm and pretty much new everything.

All of our existing data is contained in our WSS_conten db.  We were able to rebuild the entire server from scratch and added the exisiting content db to our site but are not able to link to the data contained with in it.  Is that even possible?  Is there a way to either import the existing data into the site or merge with another content db?

Not sure what to do beyond this point as I'm an amateur at best with sharepoint.

We are using Sharepoint server 2007 sp2 on windows server 2008 R2.

Any help would be greatly appreciated.

  • 3
  • 3
1 Solution
Brad HoweDevOps ManagerCommented:
Yes, you can move Sharepoint content DBs everywhere :)


One the new server did you re-create you webapplication from stractch?

How did you add your existing contentDB to your restored webapp? Did you use central Adminstration?

Please provide all the steps you took,
40hzAuthor Commented:
I'll do my best to describe as tasks were shared.  I'm glad to hear that you can move db's because i would die where I sit if we lost all that data lol.

1.installed all components on server.
2.created new server farm config/db
3.created new web apps, i believe three in total (portal, personal and admin) with new content db's as you are forced to do so in config
4.added wss_content db to our portal site(http://intranet, our main site collection).  this site has the same host name as our existing sharepoint config.

I believe that is where we are at, at the moment.

We created a new webapp of the same name using central admin/app management/content db's and added it to the web app.  if i absolutely need too, i can get the existing webapp but cannot use the web ui at all and the site is non-functional as it sits.

I was reading this info:


Is that the route i want to go?

Thanks for the super fast reply, i think it's time for a frosty brew :)
Brad HoweDevOps ManagerCommented:
On route home now.

1. Do you have a Sql backup of the current/proper contentDB?
2. When you created the webapp, did you us the same content DB name as the existing server?

Let me know :)
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

40hzAuthor Commented:
Yes i do and will make a manual backup as we speak.  When the webapp was created, a new content db was created with a new/different name than the exisiting server.

Our old content db is sitting there with no friends lol.
40hzAuthor Commented:
I got it to work by following this site's walkthrough:


This relinked the Content DB which had also contained our original sites, libraries in a addition to our data.  This makes rebuilding much more tangible.
Brad HoweDevOps ManagerCommented:
Weekend was to busy to use a PC, glad you got it working.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now