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

Migrating Sharepoint 3.0 Internal DB to SQL 2008

Lots going on here which is making resources fairly difficult to find. I have the following configuration:
MS Sharepoint 3.0 running the internal database on a Windows 2008 Server 32-bit
SQL 2008 Standard running on Windows 2003 32-bit

I would like to migrate the content DB from WSS to SQL 2008 so I can really do some in depth reporting using SQL reporting services.

Should I do a detach and reattach? Restore from a WSS backup to SQL 2008 (is this possible)? Do a backup and reinstall everything properly with the database config?
0
LeifHurst
Asked:
LeifHurst
1 Solution
 
static-voidCommented:
Personally i would back it all up then do an upgrade on your sql box, its worked for me in the past... the other options will both work, personally i prefer backup restore.
0
 
static-voidCommented:
oh actually one thing you should know is that you can only really backup and restore content databases. this means you need to reconfigure your farm which may be un-desirable
0
 
static-voidCommented:
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
nishant_shah_2002Commented:
0
 
zephyr_hex (Megan)DeveloperCommented:
you said:
"MS Sharepoint 3.0 running the internal database on a Windows 2008 Server 32-bit"


this means that you'll need to uninstall and re-install sharepoint. when sharepoint uses its internal db, it gets installed as standalone.  in order to use something other than the built-in sql, you have to uninstall, and then re-install using the farm/advanced option.  even if the full sql version is on the same server as sharepoint.

as for the steps to get the content from the internal db to full sql:
http://technet.microsoft.com/en-us/library/cc262018%28office.12%29.aspx

0
 
LeifHurstAuthor Commented:
This worked for us. Uninstalled everything and restored the content databases to our SQL server. Went ahead and took this time to upgrade everything to 64-bit as well.

Thanks again!
0
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

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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