Geeks With Blogs
Michael Van Cleave Traveling the technical world, learning the language
Well, as promised quite a while ago I was finally able to get this accomplished for the client I am working with.  But before I go in to the steps that I used let me re-iterate the situation.

My client has had a Team Sites box setup with WSS 2.0 for a while.  This was mainly just for the use of team sites for projects and planning things.  It didn't support the whole company, but made it possible for a team to work on a project/issue in a central place.  The box was never meant to be a production box and never was it configured and administered in a production way.

With that said the WSS 2.0 implementation contained 4 top sites and a total of 141sites.  The database that contained all of the data was in the range of 20GB on a SQL Server 2000 database server.

So on to the steps and lessons learned....

Step 1: Check Service Pack Level
     
The first thing to verify before you do anything is to check the service pack level of your current 2.0 SharePoint installation.  I found that it was still running SP1 and had never been upgraded to SP2.  This presented a huge problem.  At a minimum your SharePoint 2.0 installation has to be at the SP2 level.  If found this out when I had the database backed up and restored to my new database server and tried to attach it to MOSS 2007.  It came back saying that the database was too old and couldn't be upgraded.  So if you get a similar error message, double check the service pack level for your 2.0 installation.

Step 2: PreScan
       
With the installation of Services 3.0 or MOSS 2007 comes a nice little utility to help you pre scan the 2.0 install for things that might cause errors when you migrate.  You can find this utility on your 2007 server under <%root%>\program files\common files\Microsoft Shared\web service extenstions\12\bin directory.  Transfer the EXE to your 2.0 server and kick it off from the command line.  The command line statement “Prescan /all” will start the utility and have it start enumerating all of the sites on the box. 

      When it is complete it will put a log file in to your Documents/Local Files/Temp directory with information as to what it found.   It details any errors that it encountered, it details lists that it re-organized, and also will give you details on page customizations and the like.  Verify that there are no errors,  If there are, fix them before you do the migration.  Rerun the prescan utility after repairing any errors to be sure that things have been rectified and are good for migration.

Step 3: Backup/Restore
      I didn’t have the opportunity to do this part of the operation.  I had a fellow DBA do this part for me, but it did take quite a while.  The issues he encountered here was that every time he tried to transport the backup files from one server to the next it kept on corrupting.  So the solution was to use a compression utility to zip up all of the data and then transport it.  That seemed to do the trick.

Step 4: Create New SharePoint Web Application
     
Now if you have been working with and configuring SharePoint 2007 then more than likely this will be second nature to you, but there is one little step that is a bit different here.  When you create a new web application usually it will default to create a new content database usually with a name like “WSS_Content_<GUID>”.  If we were just going to create a new web app this would be fine, but we are looking to attach a copy of the old WSS 2.0 database to this web application.  So, replace the defaulted name of the database to the name of the newly migrated and restored database from the WSS 2.0 and let it rip.

      SharePoint will take over and create the web application, but instead of creating a new content database it will upgrade the 2.0 database to the correct schema that 2007 uses.  Once that is done you should be able to access your content through the new url root.  I did go through and verify that it did bring over all of the content as well as the security settings for the sites. 

Step 4b: I don’t want a new SharePoint Web Application
     
Okay, so what if you don’t want a new web application?  Well you can always do the same thing by attaching the migrated database to an existing web application on the 2007 box.  You can do this either by the content databases interface in Central administration OR you can do it with STSADM.  I would recommend the STSADM method for the only purpose that when you do the attaching and upgrade the process can take a bit of time and can possibly time out the Central Administration operation.  The only issue I found with this process of attaching and upgrading is that if your 2.0 site structure had a top site (which most of all will) it will not be pulled in and overwrite the current site collection of the existing web application.  At least, I found that the content at the old top site I had couldn’t be accessed.  So I chose to go the path of Step 4 above.

      The STSADM command line statement looks a bit like this:  stsadm –o addcontentdb –url <web application url> -databasename <database name> [there other optional switches you can add on if you would like but this is the base execution].

Well, I hope that this has proved useful for anyone in the need to do this type of upgrade.   Again, during this process I didn’t have to really mitigate any major errors or deal with any major customizations that might have been done to the 2.0 installation.  I guess I was lucky in that respect, but with other sites that might have 3rd party web parts or other customized parts you might want to really proof out the process you will use to do the migration.

Happy Coding.

Michael

Posted on Tuesday, May 8, 2007 11:42 AM | Back to top


Comments on this post: Database Migration from WSS 2.0 to MOSS 2007

# Link Listing - May 9, 2007
Requesting Gravatar...
Garage Sales and Garage-Sale Quality Code [Via: Scott Hanselman ] MooTools 1.1 Released [Via: Dion Almaer...
Left by Christopher Steen on May 09, 2007 11:09 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

Its a very good article, thanks for sharing it.

I have one query.
Do I have to upgrade SPS2.0 to SPS3.0 before taking database backup and restoring it on to SPS3.0 box?

Thanks in advance.
Sachin
Left by Sachin Dekate on Jun 18, 2007 3:07 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
No, you just need to run the prescan utility.

So you prescan the 2.0 box, that will modify some things in the database, then you take the back up of the 2.0, and restore it to another database. Then when you are creating a new web application in your 3.0 installation, you type in the restored database name and SharePoint will automatically upgrade it for you.

If you don't run the prescan utility before you take the backup, you will get an error message when you try to upgrade it.

HTH.

Michael
Left by Michael on Jun 18, 2007 6:31 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thanks Michael,
We have done exactly what have you described. But up gradation did not happened it seems. We can see database has attached form content database of central administration, but not a single site has came due to up gradation.

Is there any step left after = stsadm.exe -o addcontentdb;

OR we are missing something?

Any Idea ???

Sudip
sudipmisra@hotmail.com
Left by Sudip Misra on Jun 18, 2007 7:24 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Have you tried to get to your sites using the web application you attached it to? If so, then try to add it via the Central Admin.

Michael
Left by Michael on Jun 18, 2007 5:08 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I have tried to add contentDB from "Central Administration > Application Management > Content Databases ".

Even that does not works.

Please put some light on this.

Thanks
Sudip
Left by Sudip Misra on Jun 19, 2007 1:22 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thanks Michael,

After running the PreScan tool, it worked.

Sachin
Left by Sachin Dekate on Jun 19, 2007 6:30 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Excellent.

Glad to hear that.
Left by Michael on Jun 19, 2007 12:23 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Sudip,
When you add the migrated DB, are you setting it to be the default database? If not give that a shot. I should have upgraded when you added it to the web application.

If all else fails, create a new web application and specify the database name as it's content database when you create it. See if you get an error or if you are able to get to the content.

Michael
Left by Michael on Jun 19, 2007 12:26 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I have a top level site in my content db and its url is like "http://abc.xyz.com".

After migration (I tried exactly same as u explained in step 4. and using command line also) its creates the site collection as "http://abc.xyz.com" but I am not able to access that. I have made entries in host file also

basically I have two url's now. one is of web application and another of my site collection. but both doesnt work. I tried giving both as same but no sucess.

I checked the migrated db and its show all proper webs as of my old site.

kindly help me to fix this.

also r there any know issues or limitations of this approch. out of all three which u feel is best & safe for large databases.

Left by Dattatray on Jun 20, 2007 6:53 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I have a question regarding restoring the SQL database to the new server farm. I have tried restoring this database through Enterprise Manager > MS SQL Servers > SQL Server Groups > (local) (WinNT) > Databases.

I have right-clicked and All Tasks > Restore Database.
This is where I'm a little confused. Do I restore an actual database? What I mean by that is do I "Restore as database:"? If so, which database to I restore it to? If not, then how do I get my backed-up db into SQL?

Any help/advice would be helpful.

Thanks
Left by Jason P. on Jun 20, 2007 12:42 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Dattatray,
I think you are having a problem with the url. If you upgraded the database with a new web application the url will probably look something like this:

http://<servername>:<port>/<sitecollection>

If you want to change the server/port name you will have to supply an alternate access url and then add a dns entry to point your url to the correct IP (or use your hosts file).

The other thing you need to check is if you supplied a Host Header when you created the web application. If you are not creating this on port 80, then that could also be some of your complication.

Michael
Left by Michael on Jun 20, 2007 11:38 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Jason,
I had to do this a couple of weeks ago and had the same questions. But here is what I figured out.

In Enterprise Manager, create a new database.
on the database, select All Tasks, Restore Database.
If you are using database backup files (.bak) then you will select from file.
Navigate to the file, and select it.
Then, there is an options tab or advanced tab on the dialog, select it, and find overwrite existing database.
Select the database that you newly created as the database to restore to and you should be good.

I was able to find some good documentaion on it on MSDN. Just look up Restoring Sql Server Databases.

HTH

Michael
Left by Michael on Jun 20, 2007 11:47 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Michael,

I followed your steps and was able to get a sharepoint 2.0 site running in Sharepoint server 2007. I do seem to have two problems that are arising. The first issue is that I can not seem to access anything but the home page, all sections give me forbidden. I have set a user as the administrator of the site, but that user can not access anything...

My other issue is that the site has not adopted the sharepoint 3.0 interface. This site was a straightforward 2.0 site with no customizations. What do i do so that it will show correctly in 3.0? I am missing some of the important features that way.
Left by jbardrof on Jun 29, 2007 10:34 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
jbardrof,
You may need to give yourself full control rights to the site collections for the web application. Under Application Management in Central Admin, click Policy for Web Application, Add Users, Select the web applciation in question, Next, enter your username and Check Full Control, then Finish.

This will give you complete admin rights to everything on the Site Collections on the specific web application.

The sites not picking up the 3.0 site look and feel is strange. The ones I migrated picked it up immediately. The only ones that didn't pick it up were the ones that were customized. Be sure that maybe someone didn't create a custom site template that was used to create all of yours sites. It might look original, but if it was modified in any way at all then it is considered customized. That is the only thing I can think of why it wouldn't have picked up the new look.

Michael
Left by Michael on Jul 02, 2007 10:22 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thanks for your detailed information, but unfortunatly we run during the upgrade of the content database in an issue for which we dont find any solution.

We have areas in SPS 2003 with individual rights independent from the basic rights defined for the portal.
Everytime an area is processed during the upgrade an error is thrown that claims that the username contains invalid characters. Unfortunantly this is not the case I renamed an user to "test" and got the same error. Even the predifend websitegroups throw this error if the rights for a specific area differ slightly from the standard.

I found two other entries with similar problems but without a solution.

Even if you dont have a hint do you perhaps know where the security informations are stored in the database tables of MOSS 2007? Who has access to which elements and so on.
For a try I renamed the logins for all users which took me a step further only to accounter the issue with the websitegroup mentioned above.

Just to mention it the prescan mentioned no issue. In our case of the upgrade each step forward seems to be one or even two steps back.

Left by Daniel on Jul 04, 2007 10:32 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
hello -

we used step 4b (stsadmn) but now wish we had followed step 4 instead. Is it possible to go back at this point? Should I just restore the database and go back to 4? Can you detail the steps for 4? thanks
Left by Doc on Aug 02, 2007 7:22 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Doc,
Yes, you can delete the web application with out deleting the database, then recreate it using step 4.

But, this might be a short lived hooray if the database is pretty big. It is possible that if the upgraded database is too big that it will tell you that you need to attach it with the STSAMD command.

What type of problems are you having with using the STSADM command?

Michael
Left by Michael on Aug 04, 2007 8:17 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Dear Michael:

Thanks for answering all our questions. I have one pertaining the migration in my own group:

We have an externally hosted WSS v2 solution; they have confirmed that they can only supply us with a STSADM backed up copy of the database for our site collection (db backup format: .dat). We currently have set up a local deployment of MOSS 2007. Is there a straight-forward way to connect the db bkup to it?

While researching, I understand that taking a SQL bkup of the content db of a site collection, I can reconnect that within MOSS 2007. But I'm assuming that the STSADM bkup is not actually the content db is it?

I hope my question is not too confusing. My group is really stuck on this; any help you can provide would be greatly appreciated.

Bo Yang.
Left by Bo Yang on Aug 07, 2007 12:48 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Bo,
Yeah, there is not really an easy way to get there, but it might be possible.

You need to set up a v2 environment to the same exact version that the hosted environment was (this is a big deal, if the versions do not match then the backup will not restore to the v2 environment), then restore your content. When you do this, then you can follow the steps above to migrate the database or do what ever type of upgrade that makes sense for your organization. But, no. The backup you are getting is not the database but the content with manifest files detailing the content and how to restore it to an existing v2 environment.

I wish you luck. The last v2 backup I tried to restore I had tried just about every version possible and could not get the file to restore. I might have been doing something wrong, but if you are able to get it to restore then you are pretty much home free.

Michael
Left by Michael on Aug 08, 2007 12:20 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Great Article, I followed it, and my WSS2 database seems to be migreated ok, but noting works :-(

I installed a new WSS3 system
Created a new Web Application and pointed at the WWS2 database
Created went well, database seems to be migrated.
Skipped site creation
Noting works...

Hitting a URL in the new system gives tis in the log:

2007-08-16 16:08:34 W3SVC515821782 10.4.152.10 GET /notezone - 80 - X.X.X.X Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+InfoPath.2;+.NET+CLR+2.0.50727) 401 5 0
2007-08-16 16:08:34 W3SVC515821782 10.4.152.10 GET /notezone - 80 - X.X.X.X Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+InfoPath.2;+.NET+CLR+2.0.50727) 401 1 0
2007-08-16 16:08:34 W3SVC515821782 10.4.152.10 GET /notezone - 80 PUNISHER\Administrator 193.108.190.140 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+1.1.4322;+InfoPath.2;+.NET+CLR+2.0.50727) 200 0 0

So, I get 401 errors... and what is the last line where punisher\Administrator makes a request?
Left by Normann P. Nielsen on Aug 16, 2007 1:20 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Normann,
Hmmm.. This is the strange one. Are you logging in as the administrator? If not, you might go back to the Central Admin and add a policy to make you a full control administrator of that web application.
I have no idea what the punisher\administrator is, unless your machine or domain is punisher and you are logged in as the administrator.

Michael
Left by Michael on Aug 20, 2007 10:41 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hello,

I just performed your steps and after a couple of snags on my end with permissions to DB, everything came over as expected. I guess because of customization we made the sites they kept the 2.0 look and feel, so I was a little disappointed with the conversion, but at least I got all of the data over. Unfortunately the site I wanted to come over didn't because of some custom webparts we used.

These have been the most through and complete directions I have found.

Thanks again,

Andrew
Left by Andrew Wong on Aug 29, 2007 1:38 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Andrew,
You might just need to get a copy of the dll that has your old web part in it and put it on the new sharepoint server, and then declare it as a safe control. This will probably alleviate the problem with the site you wanted to come over.

On the other sites that still have the 2.0 look and feel it is because they were modified with FrontPage. To convert these to the 3.0 look and feel, use SharePoint Designer to attach to the sites and revert that pages. This will roll them back to the ghosted pages that come along with 3.0.

HTH

Michael
Left by Michael on Aug 29, 2007 1:47 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thanks, I was able to find the old Webparts installers and I installed them in my dev sharepoint environment and got the site working. Thanks for the suggestion.

I also tried the Sharpoint designer approach to getting the 3.0 look and after looking at the results I think I will just spend the time rebuilding the sites in 3.0 and then port the data over the best I can.

Thanks again for the document and the suggestions.

Andrew
Left by Andrew Wong on Aug 30, 2007 3:50 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael

I'm currently tasked with scoping out the effort required to upgrade a bunch of WSS 2.0 collaboration sites to WSS 3.0 (not MOSS 2007). I was wondering what kind of variables I should consider that would influence the time line (e.g. how many sites in total, what kind of customizations had been implemented, etc)? In your opinion, from your experience, would you be able to ball park the number of days a typical upgrade project would take?

Appreciate any kind of advice you can give me.

Many thanks
Stan
Left by Stan on Sep 12, 2007 6:11 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Stan,
That is a terrific idea. I would say what made the transition easiest for me was to set up a development environment like you have in production (or as close to it as possible) then follow the database migration strategy listed. This way you will know what sort of issues you will hit, and also you will have a working development copy to test out the process on.

I did find that doing an audit of all of the sites and also listing the sites that have customizations and custom web parts will help immensly. This way you can track down the custom web parts and things before you do the roll over. I would do test migrations until you are satisfied with the process you have developed and then you will know exactly how long it will take you. The process you create will probably take a couple of days, but then you would be armed with exactly how long it will take and you will go in to the migration fully loaded and ready to get it done right the first time.

Michael
Left by Michael on Sep 12, 2007 7:57 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

Working on - Your article really proved to be "golden" to me. I have now (almost) finished my 2 upgrades with success, please read the complete story here: http://www.mos-eisley.dk/sharepoint/Wiki%20Pages/My%20WSS2%20To%20WSS3%20Upgrade.aspx
Left by Normann P. Nielsen on Oct 02, 2007 12:11 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Excellent. I am glad that it was helpful. That was the point. Also, it looks like you have had to diagnose some interesting challenges yourself that will hopefully be helpful to others as well. Bravo!

Michael
Left by Michael on Oct 02, 2007 8:27 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hello -

I am trying to upgrade my WSS2.0 site but I am upgrading first in a test lab environment just to ensure that everything goes smoothly. When I ran the prescan /all command I get numerous errors in the resulting PRESCAN.log file such as "FAILED to persist field schema of lists in web" and here's what my summary in the PreUpgrade report looks like:

10/03/2007 10:00:18 Number of sites skipped (already scanned): 0
10/03/2007 10:00:18 Number of sites scanned: 9
10/03/2007 10:00:18 Number of broken sites: 9 (100% of total).
10/03/2007 10:00:18 Number of webs scanned: 103
10/03/2007 10:00:18 Number of broken webs: 91 (88.35% of total).
10/03/2007 10:00:18 Number of webs using custom template: 11 (10.68% of total).
10/03/2007 10:00:18 Number of pages scanned: 12465
10/03/2007 10:00:18 Number of unghosted pages: 2481 (19.90% of total).

I would like to proceed but I need to know how to fix these errors first. Any help would be most appreciated. Thanks!

--GREG--
Left by Greg Tompkins on Oct 03, 2007 12:40 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Greg,
I was fortunate in the fact I didn't run in to many problems when I was doing the migrations I have done. But, I did however do a bit of research on the error you are getting and it looks like it is synonomous with having an orphaned list in your DB.

Bill Baer put together a great blog about the different errors you might find and what they mean. You can check it out here.

http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

Good Luck.

Michael
Left by Michael on Oct 03, 2007 12:56 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hello Michael,

Excuse my ignorance but I'm kind of new at Sharepoint and I don't understand the concept of "orphaned lists". Could this be happening since I restored the contentDB from one server in one domain to a test server in a test domain? Do I need to recreate the virtual servers (in IIS) and application pools exactly like they are on the production side. Thanks for your help and the link to the additional resource. Unfortunately Sharepoint support in India hasn't been much help in my project.

--GREG--
Left by Greg Tompkins on Oct 03, 2007 1:18 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hello-

I found a doc. about prescan errors. I am getting "FAILED to persist....." message and according to the doc, it says its due to orphaned lists. But when I run the stsadm command it says I don't have any orphaned lists. How do I ensure all the lists have parent sites?

Thanks,

--GREG--
Left by Greg Tompkins on Oct 03, 2007 4:29 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Greg,
You might just continue with the migration then. It sounds like you might just be running in a circle. After the migration then cruise the sites and see if you see any obvious problems.

Michael
Left by Michael on Oct 03, 2007 7:36 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi-

I tried to attach my database in 3.0 and I'm getting this error now...

Attaching this database requires upgrade, which could time out the browser session. You must use the STSADM command 'addcontentdb' to attach this database.

Thanks,

--GREG--
Left by Greg Tompkins on Oct 04, 2007 11:26 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
yeah, this is pretty common when you have a pretty decent size database that you want to attach. You will need to connect the DB via the STSADM command line utility.

Michael
Left by Michael on Oct 04, 2007 11:35 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
OK -

I ran the stsadm command and I only got THREE errors, which I think is quite remarkable given my 20GB sharepoint contentDB!

Now my problem is I don't see the contentDB in Sharepoint administration and if I try to add it I get the same error.
Left by Greg Tompkins on Oct 04, 2007 12:26 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
This is the command I ran and the output....

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa
dm -o addcontentdb -url http://itdlabsrv04 -databasename orjudicial -databaseser
ver ITDLABVSRV05

Upgrade completed with errors. Review the upgrade.log file located in C:\Progra
m Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log.
The number of errors and warnings is listed at the end of the upgrade log file
.

When I go to Central Administration > Application Management > Content Databases all I see is this: There are no items to show in this view. under add a content database.

If I try to add it in here, it says to run the stsadm command, which I do and then it doesn't show up under Content Databases. This whole upgrade process has kept me chasing my tail in circles.

Thanks for all your help!

--GREG--
Left by Greg Tompkins on Oct 04, 2007 12:35 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Michael

I have tryed doing the upgrade both ways which you have stated and have run into the following errors

If I create a new application with the Database the web site times out.

If I add the database to an existing application then it adds it but does not upgrade it and stats there are 0 sites in the database where there should be 1072 sites.

Can you think of anything which could be the problem except for the fact that we have alot of sites.

The only other thing which we have is that we have got Project Server installed on the WSS 2.0 server, but the upgrade for that stats to upgrade SharePoint first.

Hope you can help
Left by Mick on Oct 10, 2007 9:09 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Mick,
Hmmm.. When you add the database to an existing web application, are you deleting the previous default database or setting the upgraded one to be the default?

I have a feeling that the database in getting upgraded, but for some reason SharePoint is not seeing the upgraded database as the default database for that web application.

Michael
Left by Michael on Oct 13, 2007 9:20 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
@Michael:

If i do a Database-Migration from SPS2003 to MOSS 2007 and run the prescan on the SPS2003. Will that do any changes to my SPS2003 Configuration or Content? This is my Production-Server and should be available for a while before i publish the new Web on MOSS.

Ron
Left by Ron on Oct 15, 2007 2:18 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Ron,
I am not positive if it does change something or not, but MOSS does know if you have run it, so I would assume it does change something. However, I have never run in to a problem after running it. Really all it will do is vaildate and run checks on your data to be sure there are not going to be any problems with the upgrade.

But I would definitely say, if you could build a development environment, I would recommend that for complete saftey.

Michael
Left by Michael on Oct 15, 2007 7:58 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi, I am trying to do a database migration/upgrade from WSS 2 to WSS 3. I have 17 WSS 2 sites which are all contained in the same content database. All 17 WSS 2 sites are configured to be accessed via host header...such as site1.domain.com, site2.domain.com, etc. I was able to backup and restore the WSS 2 DB to a new WSS 3 DB/web app on a new server successfully, however, I can only get to one site of the 17 (I'm guessing it is the first site created in WSS 2 or something).

In addition, after attaching the upgraded content database to the new web application, there is only 1 site collection in the web app (I thought the attach process would create 17 site collections -- one for each site in WSS 2).

I've looked in the WSS 3 content database, and all the sites are listed in it, but i have no idea how to get to them.

How can I migrate all 17 sites from the same WSS 2 content database?

Thanks so much!
Left by Robby on Nov 10, 2007 8:47 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I have run the prescan tool- no errors, no custom web parts. Then we made a copy of our database (SQL backup and restore).

But, now when I try to upgrade, (attach the copied database to MOSS 2007 using stsadm), stsadm complains and says that I need to run the prescan tool on the database.

I cannot run prescan on the copied database, because it is not attached to SharePoint - how do I get around this?

Thanks,
Peter
Left by Peter Rawlings on Nov 26, 2007 3:47 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
It sounds like there were database changes after you ran the prescan tool. You need to be very sure that there is no activity on the databases after the scan is run.

When I did it, the move was off hours and we had complete control of who accessed what on the database.

In short, you will have to rerun the prescan, disable the database, and do a backup. Then you should be in better shape. After the backup, you should be able to re-enable the database again, but you have to be sure that no one is making changes to the database before you do the backup.

HTH.

Michael
Left by Michael on Nov 26, 2007 8:21 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Will this work with a single server installation of WSS2.0 with a WMSDE database?
Left by Tim Sheehan on Feb 28, 2008 12:18 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Althought I have not tried it, I am not sure why it wouldn't work. All in all WMSDE is just a stripped down version of SQL Server.

HTH.

Michael
Left by Michael on Feb 28, 2008 12:29 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi,

I was doing migration from SPS 2003 to MOSS 2007
Steps i followed were-->
1) Backup SPS DB
2) Restore the SPS DB on MOSS 2007 Environment
3) Created a new site collection same as was in SPS.
4) Used stsadm tool for adding the content DB
i am getting following error-->
[DatabaseName] on [Database Server] contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database.

What should i do?

Left by Shash on Mar 19, 2008 1:04 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Shash,
Did you create a new web application or are you trying to add this content database to an existing web application? Also, did you happen to run the prescan before backing up your database?

Michael
Left by Michael on Mar 19, 2008 9:51 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Actually Shash, you might delete your new site collection then try to add the content database.

Your backed up and restored database has all of the site collections inside and I have a feeling that when you have a new site collection it is causing this error. Please try that and let me know.

Micahel
Left by Michael on Mar 19, 2008 9:54 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,
I have a multilanguage portal in cms 2002. i have to migrate the content from there to moss 2007. The content in cmsdb has a key and the corresponding content is in a custom db.When i migrate the content as it comes from cms db its coming in key.Can you tell me how to migrate the content in customdb to sharepoint 2007.
Left by Jackson on Mar 26, 2008 6:05 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Jackson,
I wish I had more information for you on CMS migrations, but unfortunately I haven't had to do that type of migration yet.

Michael
Left by Michael on Mar 27, 2008 8:56 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I have been given the project of migrating/upgrading an external site(136 sub sites)from wss 2.0 to our enterprise MOSS environment. They requested that the url's remain the same. Please help...
Left by Kay on Apr 01, 2008 1:18 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi,

I would like to know about MOSS databases structure and its tables details, please help me in getting this information

Thanks,
Guru
Left by Guru on Apr 09, 2008 8:41 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
what would be the steps to simply migrate the DATABASES to a new server... existing DB server is MSSQL 2000 new is MSSQL 2005.

We want to upgrade to 3.0 as well but are trying to take this one step at a time!

thx in advance!
Left by Kevin on Apr 09, 2008 9:35 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Guru,
Well, I would love to sit here and type up all of the tables and what they contain although I will pretty much say this. It is stated very clearly by Microsoft to stay away from the database. Either changing it or connecting to it through other sources other than the SharePoint API. If you are would like, the database is really named pretty clearly what the tables contain and if you would like to know what gets put where you could use SQL Trace to trace what happens when you perform certain actions.

Otherwise, I wouldn't recommend doing anything other than looking at it.

Michael
Left by Michael on Apr 09, 2008 8:02 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Kay,
The site relative urls are actually stored in the database, so when you move your database and upgrade it to 2007 your url structure will not change, you just need to name your site collection the same as the site collection you had in the 2.0 version

HTH,

Michael
Left by Michael on Apr 09, 2008 8:05 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Kevin,
This link should be pretty helpful for your need (http://support.microsoft.com/kb/894164). It shouldn't be all to difficult since you are just moving to different versions of SQL Server, but when you go to upgrade that is where this post will be helpful.

Michael
Left by Michael on Apr 09, 2008 8:14 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I am in the process of upgrading WSS v2 to MOSS. I attached the v2 content database and is now upgraded. However, the WSS v2 site had 136 sites all in the same content database. After the upgrade, there is only 1 site collection in the web app. I thought that the attach process would create 136 site collections(one for each site in WSS v2). What is the best process to migrate all 136 sites from the same WSS v2 content database to their own site collection?
Left by Kay on Apr 14, 2008 1:40 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I am in a process of migrating an SPS 2003 site to MOSS 2007 using Database Migration.
When I try to add the content DB via stsadm tool, it says:

Upgrade completed with errors. Review the upgrade.log file located in C:\Progra
m Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log.
The number of errors and warnings is listed at the end of the upgrade log file
.

On viewing the Log file it shows a "Timeout" type of error.This generally happens when the database size reaches 1GB range.
Earlier I had successfully migrated sites upto 800MB Database.

Kindly help me out.
Left by Neha on Apr 15, 2008 1:25 AM

# SharePoint 2007 Wiki sites vs wiki page libraries
Requesting Gravatar...
What is the difference between a wiki site and a wiki page library? Why use one versus the other?
Left by Kay on Apr 16, 2008 8:54 AM

# document libraries, lists
Requesting Gravatar...
We upgraded our 2003 to 2007 about 6 months ago. We have not gone live yet as we are still working on the master page/page layouts/webparts. Can I use this process to migrate the document libraries and list data without disrupting the new page layouts/master page templates we've created?

Thanks
Left by James on Apr 17, 2008 5:30 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Ivar,
Be sure that you have SharePoint updated with SP1 and any other applicable hotfixes. I remember running in to this before SP1 and Microsoft had me install a Hotfix that hosed the farm I was working on. You can find that in another post, but I believe that the SP1 upgrade includes the fix for any 500 Internal Server errors. Also, be sure to look at your log files and Eventlogs for any clue as to what issue might be causing the problem.

HTH.

Michael
Left by Michael on Apr 22, 2008 6:23 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
James,
You might be able to. However if you have any pages that have been customized (or unghosted) then it will show the master or modifications before the migration. It might be worth investigating the content deployment features in MOSS. That might of some use.

Michael
Left by Michael on Apr 22, 2008 6:30 PM

# Site Collection Administration section not visible on Migrated portal (WSS2.0 to MOSS 2007)
Requesting Gravatar...
I was able to successfully migrate from WSS2.0 to MOSS 2007 (yes not WSS3.0). I just created a new web application and consumed the restored DB from WSS2.0 world and MOSS migrated it fine. I did not create any new site collection.

But I found the following issues on the new migrated portal on the MOSS server:
1) Not getting "Site Collection Administration" section in Site Settings.

If is as if there is not site collection and it is treating this as just a site.

How do I get the Site Collection Administration section with all the links in it?

2) Not able to activate Office SharePoint Server Publishing feature. When I try to activate that feature I get the error "One or more features must be turned on before this feature can be activated - Office SharePoint Server Publishing Infrastructure".

I also went an manually (using stsadmn) activated Publishing Prerequisites and then various Publishing features. But then I when I come back this "Office SharePoint Server Publishing" feature is still not activated in Site Settings > Site Features section.

Thanks for your help!
Left by MOSS_Explorer on Apr 24, 2008 9:51 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Supported path is WSS2.0 to WSS3.0 to MOSS
Left by Anonymous on Apr 25, 2008 2:21 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Almost all our existing SPS 2003 sites are using the 'Team site' template.
Is there a way I can apply custom template to existing sites when they migrate over to MOSS 2007? What I am trying to do is to limit the amount of functionality available to begin with for these sites.

Here is what my plan of action would be:
I will create a custom Team template (based on team site template) in MOSS 2007 and when the SPS 2003 sites are migrating they should take custom template instead of the default Team site template.

I am also fine with changing template type for sites after migration if that is possible.

Thanks!
Left by Manish on May 01, 2008 9:15 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I installed the sp, but still the "500 internal server error" poped up.

Then I installed the language pack and it worked fine.

I had only the 1044 (norwegian) folder under
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\

Needed to have the 1033 folder - english.

Thanks, this upgrade is brilliant.
Ivar
Left by Ivar on May 06, 2008 3:38 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Seems kind of strange that you don't have a 1033 folder under your install of MOSS. Have you checked your application logs and SharePoint logs to see if there is a specific error that is being created?

Michael
Left by Michael on May 06, 2008 7:25 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Manish,
Although I think I know what you are looking to do I am not sure there is a way to do it unless you change the site definition on the file system before you make the transistion. I wouldn't recommend that. The site template is referenced in the database for the site so you might have troubles if you try to make a modification during the transition. All in all, I would steer away from doing this during the migration.

Michael
Left by Michael on May 06, 2008 7:30 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
My Sharepoint 2003 team site's database is on SQL 2000. I ran the prescan utility, few errors, fixed them.. Got the database over to the Sql Server dedicated Sharepoint 2007, which is running SQL 2005. Went fine. But when I try to create a new web application or add a content database from te Content Database function from Central Admin, I get an "Unknown Error". Any ideas?
Left by Jack on May 23, 2008 11:23 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Jack,
Did you happen to look at the sharepoint logs that are located in the 12 directory? You should find something in there that will detail the reason you are getting a error. Also be sure to check the applicaiton log. If you are lucky it might have some information there too.
Left by Michael on May 23, 2008 1:44 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Michael,

The only thing I Can find is "Attempting to set the HttpErrorsExistingResponse for the iis web site, DevelopmentTeam. HttpErrorsExistingResponse could not be set successfully. This may be expected for some versions of IIS. I will clear all logs and try again next week. Thanks.
Left by Jack on May 23, 2008 4:13 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I have ran the pre-scan tool from the server hosting 2003.. It scanns to 100%, completes with NO errors..

When i move the db over to my new moss 2007 server and try to add it as the content database.. it keeps telling me the pre-scan has not been ran..

where could i be going wrong??
Left by Ryan on Jul 17, 2008 5:10 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Ryan,
That is very strange. Are you running the scan then immediately packaging your database to be moved? Also, are you absolutely sure you are moving the correct database? This is the first time I have heard this type of problem pop up.

Michael
Left by Michael on Jul 17, 2008 9:20 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Michael,
I upgraded from WSS 2.0 to WSS 3.0 on a server that I plan to eventually use as a production server. I have customized the new WSS 3.0 site with new web parts, lists, wiki, permissions, etc. We are still using the WSS 2.0 site. Is there a way to get just the data from the WSS 2.0 site into the WSS 3.0 site without overwriting all the customizations? Also, do I need to run the prescan tool on WSS 2.0 again? Thanks.
Left by boomer on Jul 24, 2008 6:34 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Boomer,
If you continue to use and customize the 2.0 site then yes you will need to re-run the prescan tool before you migrate the database again. However if you just want to move documents then I would recommend looking in to a tool that will do just that. Quest makes one, but it definitely is not cheap. Otherwise you would need to move the database again from 2.0 (probably to another site collection that doesn't have your customizations), then move the documents to the site with your customizations. Either way it will be a lot of work unless you find a decent tool.
Left by Michael on Jul 24, 2008 8:17 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I have a different scenario here. I have Sharepoint Server 2003 and it is in Production environment.

I have got a task to upgrade it to MOSS 2007 however on a different server (a test server). And Sharepoint Server 2003 is not installed on this test machine.

I have no clue how to do it. I have Google it and got some command to do that however they are not working. :(

Please help.

Thanks in Advance.

Gaurav
Left by Gaurav on Oct 07, 2008 1:02 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Gaurav,
What command are you trying to run? Is it the prescan? You have to realize that any upgrade tools that you will need to run against your 2.0 environment will only come installed on a 3.0 server. You then need to copy the tools to your 2.0 server to run them.

Michael
Left by Michael on Oct 13, 2008 9:01 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi,

I'm googling for any migration info, and I came across this site. I did this upgrade, but our company Sharepoint Home page (sharepointURL/default.aspx) still looks like 2.0. All subsites (team sites, and even any deeper pages on the main site - settings, etc.) look like 3.0. I just can't figure out how or why our top-level page is like this, so I was wondering if you came across this in your experience (maybe this is even a common issue, although it seems quite strange to me :).
Left by Whitney on Oct 22, 2008 12:43 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Whitney,
The only explaination I would have for that is if the home page (Default.aspx) was unghosted and modified by FrontPage 2003. In that case it wouldn't be strange at all and you would be seeing the database copy of the modified page. If you would like to roll it back you can attach to the SharePoint site with SharePoint Designer 2007 and revert it back to definition.

HTH,

Michael
Left by Michael on Oct 22, 2008 1:45 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thank you, thank you! Resetting it to the definition did the trick.
Left by Whitney on Oct 23, 2008 11:37 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Great.

I am glad to be of service.

Michael
Left by Michael on Oct 23, 2008 2:02 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Tom,
Here is what I can find. You have to do a DB repair that will clean up the orphaned items.

Here is the link:
http://support.microsoft.com/kb/923904/

HTH,

Michael
Left by Michael on Nov 25, 2008 7:38 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thank You..
Left by Rüya Tabiri on Nov 26, 2008 9:44 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael,

I have SPS 2003 and project server on same server and project server is also using same content database to which i want to migrate to MOSS.When i am using content data base migration approach then it is not working however i do not receive any error in prescan log and upgrade log. Is Project server creating the problem?
Can you please suggest the solution for such type of migration?

Thanks,
Tarun
Left by Tarun on Dec 10, 2008 11:34 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Tarun,
I would think that it would be the problem. Generally if you look at your logs on the MOSS box then you might see that it is looking for a particular template or something when you are attaching the database.

I haven't personally upgraded a project server implementation so I am not sure if I would be able to help you much with that upgrade. However I know that people are doing them so someone must have blogged about it.

Michael
Left by Michael on Dec 11, 2008 9:37 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Jeff,
I have only seen this issue when someone is trying to upgrade from a 2.0 version of SharePoint that was assoicated with Small Business Server or another server that used SharePoint as a part of that tool. Generally the templates that the servers have available are not a template that is available in the default templates that are installed in WSS or MOSS. There are extensive threads about this in the Microsoft TechNet Forums.

I hate to pass you off to the Forums, but like I said there are some extensive explainations on the problem there and also might be an easy solution too.

Good Luck,

Michael
Left by Michael on Dec 17, 2008 6:30 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Good Luck.

Michael
Left by Michael on Dec 18, 2008 5:25 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Thank you...
Left by granit on Mar 14, 2009 1:58 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Is it just me or is the text in this article very small?

Anyway, thanks for the tips!
Left by Makolyte on Aug 06, 2009 8:31 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
I am migrating from v2 to MOSS 2007. my pre-scan shows two errors:
Error: The following site has not been scanned. Id = 055fce4c-7112-473c-b99d-7199af7aaeb5 and Url = /
and
Error: Prescan has encountered sites or lists that were not updated because they cannot be accessed using the SharePoint Products

i use the Microsoft suggested fixes but nothing works.
I'm in a VM pilot environment and have plenty of snapshots-so, I'm ok in that respect.

also, there seems to be much discussion re: moving/migrating the content db to the new servers.
Can I task this migration like this:
1. copy the sql 2000 content db to the sql 2005 server and reattach it.
2. run step 4 above

will that do the job ok? no customizations and the db is under 3gb.
thanks in advance.
Left by stan on Feb 10, 2010 1:33 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Stan,
You might need to do some database queries to see what site is actually the issue. From the looks of it, it could be a site collection that is corrupt or something, but the ID should make it easy enough to find.

As far as the migration tasks you have I would think that you would be okay, but with the error that you are getting on the pre-scan that could be the only hang up I can foresee.

If you are running virtually then you shouldn't have any problems, just be sure that you snapshot before you start down this path in case you run in to a snag.

Good Luck,

Michael
Left by Michael on Feb 10, 2010 1:50 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
thanks for the reply Mike.
when i run the pre-scan on the production server i get no errors. since the error points to a "/" i am confused. I can connect to the http://servername project workspace fine.
what query would i use to look for the bad site collection?
Left by stan on Feb 10, 2010 2:41 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Oh, well if you don't get any errors on the production database then just take a copy of that database and do the attach.

Only worry about the error if it is coming from a database that you will be migrating.

Michael
Left by Michael on Feb 10, 2010 2:49 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
thanks again.
are these the steps i should follow?
1. copy Proj. 2003 Content db to Proj. 2005 db server
2. attach it using Sql Mgt studio instead of stsadm?
3. Run the Sharepoint Central gui from within the Content mgt context and add the existing content db. this would update the config db, too??
would i detach the Default WSS_Content first?
Left by stan on Feb 10, 2010 3:06 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
correction on my Step 3

run Sharepoint central--from the content mgt context and add the NEW content db.
would i detach the default wss_content db, first?
Left by STAN on Feb 10, 2010 3:08 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
how does the config db get updated with the data from the new content db? do i attach a copy of that db, too, to sql 2005?

sorry for all the posts but there is so much conflicting info out here; I'd like to finish this project before the next millenium. :-)
Left by stan on Feb 10, 2010 3:11 PM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Fantastic article.
Just an query, how will the corss site groups behave on migration (detach-attach) procedure as there is no concept of cross sites?
If you know some article of whitepapers for wss2.0 to wss3.0 migration( apart this article :))

Thanks in anticipation.
Ashish
Left by Ashish on Mar 15, 2010 12:09 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi Michael. I am encountering a problem which I don't believe is an environment specific behavior. Essentially a document library, that existed before the migration, has content management disabled (which is to be expected since SPS2003 does not support content types). The document library is a regular one and not customized in any manner nor does it have any event listener implemented, etc. It has about 10 user created columns. When I enable content type management on the library, the Document content type is automatically added, which is expected behavior. However, the undesirable side-effect is that all the columns are being added to this Document content type. This should not happen. Would you have any insight into this behavior and how I can prevent it? Thanks again.
Left by Ashwin Raj on Nov 19, 2012 7:30 AM

# re: Database Migration from WSS 2.0 to MOSS 2007
Requesting Gravatar...
Hi
What is the advantage of prescan utility? it just scans the sites?

If i have only 1 document library with no data, do i still need to run the utility.

I have tried to restore the backup on new server but i get the error "prescan must run on the database before migrating to new version", so i guess prescan also adds something in the database.

Any idea on this?
Left by Shafaqat on Dec 10, 2012 8:12 PM

Your comment:
 (will show your gravatar)


Copyright © Michael Van Cleave | Powered by: GeeksWithBlogs.net | Join free