.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Upgrade 2007-2010 Database Attach

Posted By:      Posted Date: October 04, 2010    Points: 0   Category :SharePoint

Hi all,

Having read many of the articles abot upgrading 2007-2010, I wanted to see if a simple approach would work.

  1. Ran the pre-upgrade checker
  2. Simply detached the DB in SQL (SQL Manager only), forcing the connections to close
  3. Copied the DB to the new server
  4. Re-attached the original DB to the 2007 server
  5. Attached the copied DB to the 2010 box
  6. Ran the shell command to attach to a web application
  • All seems to work

The content databases in question are quite simple and test units, and we are moving from the staging server to production, is this a valid approach?

Also, before I try wih a 'real' db, is there any harm done in detaching/re-attaching on the original 2007 server?




View Complete Post

More Related Resource Links

Cannot crawl sharepoint site and mysite after database attach upgrade form sharepoint 2007 to 2010.

After database attach upgrade site and mysite from sharepoint 2007 to 2010 , I have full crawl and get "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error. ( Error from SharePoint site: HttpStatusCode ServiceUnavailable The request failed with HTTP status 503: Service Unavailable. )" for mysite and get "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled." for sharepoint site. The content access account for search is "db_owner" of both of site and mysite. How do I solved this problem ?

How do I upgrade the SSP database from 2007 to 2010


I'm doing a database attach upgrade from SharePoint 2007 to 2010.
So far, I have successfully attached and upgraded my content db. The next step is to attach and upgrade the SSP database containing all my User Profile data. To do so, I have followed the guidelines from this article:



It says, that I should run this command:

stsadm -o addcontentdb -databasename [my_ssp_db_name] -url [???]


One of my questions is, what value should I set for the url parameter?

The SSP site from 2007 doesn't exist anymore in 2010, so I can't figure out what the url value should be. I have tried to set the value to the url to my upgraded intranet url, but that generates an error say

Database attach upgrade sharepoint 2010 - Help????


I am trying to migrate data from SharePoint 2007 to SP2010 Foundation using database attach upgrade Method.


I am able to Restore and Mount Database on SharePoint 2010, But Now how do I use that?

I have these questions?

1. Can do I use the restored/Mounted DB for a particular Site Collection? If yes, How?

Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]

2. I have used above command to Mount the DB, but now how do I actually access the Web pages? what URL do I use?


Kindly Help...


SharePoint 2007 Upgrade to 2010 and the SSP database (woops)


OK everyone, I got myself a little stuck on something. We upgraded SP 2007 to 2010 in test, planned the production upgrade and upgraded production using the database attach approach, everything went pretty well except...

Users complained pretty quickly that their 'My Links' were missing and that the profile information they had previousely entered was gone... hmmm... we didn't actually check that stuff during testing, oops.

Well looking at the documentation I 'quickly' realized I had missed a step during the upgrade, both in test and prod; I never upgraded the SSP database. I created a new profile service, synch'd with AD, managed meta data service is working, upgraded the mysite content databases and bam, everything was good, or maybe not so good because I'm missing profile information that was manually entered by users.

So of course all the documentation says you need to attach that SSP database during the creation of the Profile Service, well I'm not recreating my profile service... no way. Is it to late to upgrade the SSP database? Do my users just need to start with fresh profiles and suck it up or is there some way I can get that profile data into my new environment?


how to Upgrade MOSS 2007 to MOSS 2010 ?

how to Upgrade MOSS 2007 to MOSS 2010

database attach method migration wss3.0 to foundation 2010

I am confused in data base attach migration method for the follwoing scenario .Can you please give me clarity? it is urgent. We have a production system in wss3.0. I took  backup of the content database using sql servr management studio tool. Can I restore this content DB to a test environment ( on sun Virtual box with 'windows 7' 64-bit host OS) and from test env't to new production system?  If my testing is done and ready to move to new production system then How can I add the data accumulated during testing period (one month) to new prod'n system from wss3.0 system. Best regards,

Inplace upgrade from moss 2007 to 2010 fails

Hello experts I have tried without success to do an inplace upgarde of a moss 2007 installation that I would consider very basic. The upgrade process itself seems fine but after you finish the configuration wizard and it attempts to go to the upgrade status page you get The provider 'CurrentNavigation' specified for the defaultProvider does not exist in the providers collection. (C:\inetpub\wwwroot\wss\VirtualDirectories\39291\web.config line 385) When i check the upgrade errors logs im getting the following [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Feature upgrade failed for Feature 'PremiumSite' (Id: '8581a8a7-cf16-4770-ac54-260265ddb0b2') in Site 'http://ehbmossserver/mysite'. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Exception: Dependency feature with id 4c42ab64-55af-4c7c-986a-ac216a6e0c0e for feature 'PremiumSite' (id: 8581a8a7-cf16-4770-ac54-260265ddb0b2) is not installed. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: at Microsoft.SharePoint.SPFeature.HandleUpgradeException(Exception e, Boolean continue

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

Move or just upgrade SP 2007 to 2010?

Purpose We have Sharepoint 2007 sp2 running with 1 application server (w2k3, 100gb) 1 index server (w2k3, 200gb) 1 web front end (w2k3, 60gb) 1 sql 2008 x64 We want to migrate to Sharepoint 2010 STD (not beta). Action plan Backup application server, index server and web frontend Reinstall OS Win2008 x64 on app, index and frontend Install SH 2010 on app, index and frontend Put SQL link back in sharepoint 2010 Question Will this plan work and not cause more trouble than solutions?

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

SharePoint 2007 upgrade to 2010 without UI update masterpage issue

I have a public facing site on a SharePoint 2007 farm that will be upgraded to 2010.  This site has a very customized look and feel that will not initially be updated to the 2010 UI.    I have run into one small issue with 2010's handling of legacy 2007 UIs.In SharePoint 2007,  to have a different master page for the application pages and dialog boxes we utilized an HTTP Module to switch the master page on the fly.    After migrating the SP2007 into our 2010 beta test environment the HTTP Module no longer worked properly.   I did some debugging and found out that SharePoint 2010 is returning a NULL value for MasterPageFile property on the pages in the _layouts folder.   I would have expected to see the URL pointing to the application.master page (or dialog.master).   Any ideas if this is a bug in SP2010 beta and will be fixed in RTM or is this the intended behavior.If it is the intended behavior in SP2010 how could I update my HTTP Module to allow the site to continue functioning as it did on 2007?   

SharePoint 2007 to 2010 Upgrade AND Farm Merge


Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

Failed upgrade from wss 3.0 to moss 2007. Cannot open database "ProjectServer-live_Published" reques


While trying to upgrade from WSS 3.0 to MOSS 2007 the process finished, but it stated that it completed with errors. Those errors seem to be causing problems within the Central Administration site. I will try outline the errors the best I can from the upgrade.log file and with the actions I've been attempting. THANK YOU in advance for any and all assistance.

[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Unable to locate SearchDatabase for the SharedResourceProvider Hyperion_SSP
[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Exception thrown was: System.ArgumentNullException: Value cannot be null.
Parameter name: No search database is associated with the search shared application, Hyperion_SSP
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.get_SearchDatabase()
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.AddNextLevelObjects()
[SharedResourceProviderSequence] [INFO] [9/23/2010 11:15:03 AM]: Re-run upgrade using stsadm -o upgrade to ensure the search database gets upgraded appropriately
[SharedResourceProviderSequence] [DEBUG] [9/23/2010 11:15:03 AM]: No search database was found, so skip upgrading it

As advised in the info section for this error I re-ran the upgrade

No Tabular View / Selection Boxes on Views after upgrade from 2007 to 2010


We upgraded one of our smaller SharePoint instances and after the upgrade and change to the new UI, the tabular / selection box's in the views are not appearing, we have to create a new view and delete the migrated view to get them to appear. This has us very concerned since this would be a major effort on our larger instance.

Has anyone else run into this? Our small instance is pretty out-of-box, we added an image to the master page, choosed an out-of-box color theme and then made a template of a site with version limits setup on the document library that we reuse to build new sites.

Looking for guidance: Integrated SharePoint SSRS migration and upgrade from 2007 to 2010


Our existing prod farm is MOSS 07 with an integrated SSRS instance using SQL Server 2008, both on Windows Server 2003 64bit boxes. SharePoint databases are on a different SQL Server 2008 server.

I have built a new SharePoint 2010 farm on Windows Server 2008 R2 boxes, using a single SQL Server 2008 R2 Enterprise server as the backend for both SharePoint databases and Reporting Services (installed in Integrated mode). We are going to be using the database-attach method of upgrading our SharePoint farm.

Is there any specific guidance out there on exactly how to migrate/upgrade Reporting Services in this scenario? I've read through some of the MSDN content (How To: Migrate a Reporting Services Installation) but nothing seems to deal specifically with doing this when in Integrated mode with SharePoint. Our business heavily relies on SSRS reports in SharePoint and also shared and custom report subscriptions via email.

We do have a dev SharePoint 2010 farm in a similar configuration that I can test migration/upgrade steps. Thanks.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend