SharePoint 2003 to MOSS 2007 Upgrade: Database migration

Of all the three upgrade techniques, my favorite is database migration. Database migration can be defined as “Requires the server administrator to install the new version on a separate farm or separate hardware, and then manually migrate the databases into the new environment.”

 

Database Migration enables moving to new farm or new hardware while SharePoint Portal Server 2003 environment is available and is untouched by upgrade. Microsoft says that database migration is a “Complex process that requires many manual steps and a higher risk of error. Requires additional manual steps to retain original URLs for sites. Search scopes must be re-created and search settings must be reapplied. Requires new server farm, and twice the amount of SQL Server storage space”. My advise is don’t be afraid and do try.

 

These steps are done for upgrade from WSS2.0/SharePoint 2003 to WSS3.0/MOSS 2007 in a single form environment. For different architecture, you may need some more steps. The steps are under: 

·     Get ready your MOSS 2007 environment.

·     Run PreScan on SharePoint Portal Server 2003.

·     Set the content database of SharePoint Portal Server 2003 as read only.

·     Take back up of content database of SharePoint Portal Server 2003.

·     Restore back up on SQL Server attached with MOSS 2007.

·     Create web application in MOSS 2007.

·     Remove content database of the newly created web application in MOSS 2007.

·     Attach restore database with the newly created web application in MOSS 2007.

 

And that’s itJ.

 

I am not going into the details of creating MOSS 2007 environment. We will start from the second step:

 

Run PreScan on SharePoint Portal Server 2003:

 

The first step is to run PreScan.exe. For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/15/sharepoint-upgrade-prescanexe/

 

Set the content database of SharePoint Portal Server 2003 as read only:

The content database of SharePoint Portal Server 2003 ends with 1_SITE like Abc1_SITE.

 

The steps for setting database as read only are:

 

For SQL Server 2000

 

1.     In Microsoft® SQL Server™ Enterprise Manager, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the Properties dialog box, click the Options tab.

3.     Under Access, select the Read-only check box, and then click OK.

 

 

For Server 2005

1.     In Microsoft SQL Server Management Studio, right-click the name of the database that you want to set to read-only, and then click Properties.

2.     In the left pane, click Options.

3.     In the right pane, under Other options, under State, next to Database Read-Only, click the down arrow, and then select True.

 

Take back up of content database of SharePoint Portal Server 2003:

 

For details kindly visit the following blog:

 

https://farhanfaiz.wordpress.com/2008/05/16/sharepoint-2003moss-2007-take-back-up-of-content-database-in-sql-server-2000-and-sql-server-2005/

 

Let the name of the back be “Portal_Site.bak”. Wait after this. The time of database backup depends upon the system power and database size.

 

 

Restore back up on SQL Server attached with MOSS 2007:

 

The first step in restoring database is to create a database in SQL Server 2005. Let the newly created database name is “Portal_Site_Restore”.

 

1.     Expand Database “Portal_Site_Restore”, right-click the database you want to restore, point to Tasks, point to Restore, and then click Database. The Restore Database dialog box appears.

2.     On the General page, the name of the restoring database appears in the To database list box.

3.     In the To a point in time text box (if using SQL Server 2005 Enterprise Edition), retain the default (Most recent possible).

4.     To specify the source and location of the backup sets to restore, click From device, and then specify the database backup path (in our case, it is “Portal_Site.bak”) in the list box.

5.     In the Select the backup sets to restore grid, select the backup path.

6.     From the options tab, select “overwrite existing database”.

7.     Specify the paths for .ldf and .mdf in the options tab.

8.     Click OK to start the restore process.

 

Wait after this. The time of restoring database depends upon the system power and database size.

 

 

Create web application in MOSS 2007

 

In the SharePoint Central Administration, move to “Application Management” and click on “Create or extend Web application” under “SharePoint Web Application Management”.

 

Again click on “Create Web application”. Set the settings according to your own needs (do check the name of the web application and content database. Let the name of the web application be “http://servername:1234” and the name of the content database be “WSS_Content_1234”) and click OK. Don’t create any site collection.

 

 

Remove content database of the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘deletecontentdb’. The description is as under:

 

stsadm.exe -o deletecontentdb

-url <URL name>

-databasename <database name>

[-databaseserver] <database server name>

 

Parameter name

Value

Required?

Description

url

A valid URL, such as http://serverame:1234

Yes

Specifies the Web application from which the content database will be detached.

databasename

A valid database name, such as “WSS_Content_1234”

Yes

Specifies the name of content database to be detached.

databaseserver

A valid database server, such as “SQLServer1”

No

Database server name to be detached.

 

A typical command will be like:

 

stsadm.exe -o deletecontentdb -databasename WSS_Content_1234 -url http://servername:1234

 

Attach restore database with the newly created web application in MOSS 2007

 

We can do that using Central Administrator or stsadm utility. I will like to do that using stsadm. Central Administration is easy. You will be able to learn that if you know how to do it using stsadm.

 

The command for removing content database using stsadm is ‘addcontentdb’. The description is as under:

 

stsadm.exe -o addcontentdb

-url <URL name>

-databasename <database name>

[-databaseserver <database server name>]

[-databaseuser <database username>]

[-databasepassword <database password>]

[-sitewarning <site warning count>]

[-sitemax <site max count>]

 

Parameter name

Value

Required?

Description

url

A valid URL 

Yes

URL of

the Web

application

to which

the content

database is

being

added.

databasename

A valid

database name

Yes

Database

name.

databaseserver

A valid

database

server name

No

Database

server

name. The

default

server

is used

if a

value

not

provided.

databaseuser

A valid user

name in the

form “domain\login”

No

Account

used for

SQL authentication. Must be

used in

conjunction

with the

database

password parameter.

databasepassword

A valid

SQL

password

No

The database

password parameter should only

be used

where Windows authentication is not

implemented.

sitewarning

A valid

integer

number,

such as

10

No

Integer number

of site

collections allowed in

the content

database

prior to

generating

a warning

event in the

Windows event log.

sitemax

A valid

integer

number,

such as

10

No

Specifies

the maximum

number of site collections allowed in

the content

database.

 A typical command will be like:

 

stsadm.exe -o addcontentdb -url http://servername:1234 –databasename Portal_Site_Restore

 

Wait after this command. The time of adding content database depends upon the system power and database size.

 

 

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

 

http://technet.microsoft.com/en-us/library/cc263422.aspx

 

http://technet.microsoft.com/en-us/library/cc262449.aspx

 

 

Advertisements

55 Comments »

  1. Jordi Garcia said

    Hi!

    Your explanation is very clear, I have follow your steps and it works fine 😉

    I have only problems migrating My Sites, when I do the last step with the Portal_PROF database stsadm command return an Error, something like “database doesn’t have a user defined schema….” The message was in Spanish and It’s possible that it could be a little bit diferent.

    Does you ever have do something like that?

    Thanks in advance! Jordi.

  2. farhanfaiz said

    Jordi,

    Following URL will help you to solve the problem:

    http://glorix.blogspot.com/2007/06/upgradingmigrating-story-continues.html

    Do let me know in case you require further assistance in this regard.

    Regards,

  3. Bramley said

    Hi

    Just everything you said above but the my content database says there are zero (0) sites. I mean this wrong I have about 34 sites in the content database. As such I can’t browse the portal. Do I have to add other database such as _prof, SERV

  4. Farhan Faiz said

    Kindly confirm that you are not restoring the same database for the second time. 😦 Look into the following post

    https://farhanfaiz.wordpress.com/2008/05/07/you-cannot-add-the-same-content-database-more-than-once-to-a-farm-even-on-different-web-applications/

  5. Bramley said

    I think I might have, so how do u resolve this issue. I looked in the config database and compared the ids with that of the Site table in my database but couldn’t find any duplications. Any ideas, The link above does say. I don’t need a duplicate copy of a site collection (or portal) in the same farm.

  6. Bramley said

    Sorry the link above does not say how to resolve the issue

  7. Farhan Faiz said

    I don’t know any resolution of this problem except to start from -1000. Install a new SQL Server and ……………

    Sorry. 😦

  8. Bramley said

    Thanks

  9. Bramley said

    Hi farhanfaiz

    I’m migrating abt 40G of content from sps2003 to MOSS2007 using the method illustrated. The stsadm takes about 14 hours to run and when is finished is says: upgrade completed with errors. When I look in the upgrade log I find the following errors.
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/30/2008 9:44:01 PM]: Table [dbo].[UserData], 2243032 Rows @ 500 Rows/s
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/30/2008 9:44:01 PM]: Table [dbo].[Lists], 701 Rows @ 100 Rows/s
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/30/2008 9:44:01 PM]: Table [dbo].[Docs], 2761275 Rows @ 100 Rows/s
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/30/2008 9:44:01 PM]: SqlCommand.CommandTimeout = 32105
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: Action 3.0.0.1000 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed.
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
    at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
    at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
    at System.Data.SqlClient.TdsParserStateObject.ReadByte()
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
    at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)
    at Microsoft.SharePoint.Upgrade.RemoveOrphanedUserData.Upgrade()
    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/31/2008 6:39:14 AM]: Begin Rollback()
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: Action 3.0.0.1000 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed to rollback.
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: This SqlTransaction has completed; it is no longer usable.
    [SPContentDatabaseSequence] [ERROR] [7/31/2008 6:39:14 AM]: at System.Data.SqlClient.SqlTransaction.ZombieCheck()
    at System.Data.SqlClient.SqlTransaction.Rollback(String transactionName)
    at Microsoft.SharePoint.Utilities.TransactionalSqlSession.Rollback()
    at Microsoft.SharePoint.Upgrade.SPDatabaseAction.Rollback()
    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/31/2008 6:39:14 AM]: Begin Dispose()
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/31/2008 6:39:14 AM]: End Dispose()
    [RemoveOrphanedUserData] [3.0.0.1000] [DEBUG] [7/31/2008 6:39:14 AM]: Elapsed time: 08:56:54.5171427.
    [SPManager] [ERROR] [7/31/2008 6:39:14 AM]: Upgrade [SPContentDatabase Name=Intranet_SITE Parent=SPDatabaseServiceInstance Name=officeserversqa] failed.
    [SPManager] [ERROR] [7/31/2008 6:39:14 AM]: This SqlTransaction has completed; it is no longer usable.
    [SPManager] [ERROR] [7/31/2008 6:39:14 AM]: at System.Data.SqlClient.SqlTransaction.ZombieCheck()
    at System.Data.SqlClient.SqlTransaction.Rollback(String transactionName)
    at Microsoft.SharePoint.Utilities.TransactionalSqlSession.Rollback()
    at Microsoft.SharePoint.Upgrade.SPDatabaseAction.Rollback()
    at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    [SPManager] [ERROR] [7/31/2008 6:39:14 AM]: Action 3.0.0.1000 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed to rollback.
    [SPManager] [ERROR] [7/31/2008 6:39:14 AM]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
    at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.Upgrade()
    at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
    [SPManager] [DEBUG] [7/31/2008 6:39:14 AM]: Elapsed time upgrading [SPContentDatabase Name=Intranet_SITE Parent=SPDatabaseServiceInstance Name=officeserversqa]: 08:57:34.
    [SPManager] [INFO] [7/31/2008 6:39:14 AM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=Intranet_SITE Parent=SPDatabaseServiceInstance Name=officeserversqa to Online.
    [SPManager] [DEBUG] [7/31/2008 6:39:14 AM]: Using cached [SPContentDatabase Name=Intranet_SITE Parent=SPDatabaseServiceInstance Name=officeserversqa] NeedsUpgrade value: True.
    [SPManager] [INFO] [7/31/2008 6:39:16 AM]: Inplace Upgrade session finishes. root object = SPContentDatabase Name=Intranet_SITE Parent=SPDatabaseServiceInstance Name=officeserversqa, recursive = False. 3 errors and 0 warnings encountered.

    Any ideas where to start on this. Please help

  10. Farhan Faiz said

    Hi Bramley,

    Can you specify errors that you are facing while trying to access the upgraded versions?

  11. Bramley said

    The upgrade is failing, therefore it fails to addcontent to http://03rnb-spsqa01:8090/

    I checked this web collection in the central administration and found out that there is no content attached. If I browse to the url: page cannot be found.

    In the log above you will see this error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Is quite generic I don’t know why this is failing.

  12. Farhan Faiz said

    Usually Time Out error is SQL Server Error.

    If you google like “upgrade SQL Server error”, you will find some good resources to sort this out.

  13. Bramley said

    Thanks Farhan, we just installed sql2005 service pack 2, and the recovering model on the database. Will see if this changes anything. So far the test is running will probably end till 2moro

  14. FYI~ There’s a typo near the end. The following “typical command” for adding the content database should be:

    stsadm.exe -o addcontentdb -url http://servername:1234 –databasename Portal_Site_Restore

    As it is now, it reads “…-o addeletecontentdb…”

    Just thought you might want to update…

  15. Farhan Faiz said

    Changed 🙂

    Thanks Toby.

  16. Gary said

    Hi Farhan,

    Great blog. Just needed one info … does this imply that all sites, sub sites from sps 2003 will be moved into MOSS 2007? Asking this since the definition of Sites in sps 2003 and MOSS is slightly different.

    Thanks
    Gary

  17. Farhan Faiz said

    Gary,

    It will move all the site but if you have some customized site definitions, the, you have to move them first.

    Regards,

  18. Jack said

    Great walkthrough! This gem saved me a lot of time. I’d spent hours upon hours trying to get the Upgrade working. I finally gave up and decided to follow your guide (wish I’d done that from the start).

    I only had one issue – step – Reattaching the Database. The command as written would not run, I had to switch around the databasename and url parameters like so –

    stsadm.exe -o deletecontentdb -databasename WSS_Content_1234 -url http://servername:1234

    Again, many thanks for taking the time to write this up. Now I can enjoy the rest of my weekend!

  19. Farhan Faiz said

    Jack,

    Thanks for comments :). Also, changed stsadm deletecontentdb command text.

    Regards,

  20. lq said

    Hi, I am asking for help because I have limited support. I never played with sharepoint until I been in the army. I been tasked to migrate Sharepoint 2003 and sql 2000 on a dell poweredge 2850 server to a dell poweredge 2950 server running sharepoint 2007 and sql 2005. I figure that I can install 2007 and 2005 on the new server and attach the sql database to 2005 and copy the sharepoint 2003 folders to 2007 but it appears to be the wrong course of action. i was able to do this fine with adobe connect but this looks like a longer process. please email me at bronxlou on yahoo to help me out. thanks

  21. Farhan Faiz said

    Iq,

    Do u have any test environment?

  22. Nizam said

    Hi Farhan,

    I have backed up SPS 2003 portal using the upgrade and restore utility. I am trying for an in place upgrade to sharepoint 2007. After the backup finished, I am unable to restore the same portal on a test server since only SITE DB gets created not the PROF and SERV DB’s. If I try your approach without PROF DB then will the user profile info into the 2007 portal be migrated. thanks

  23. Farhan Faiz said

    Nizam,

    Check the following URL:

    http://glorix.blogspot.com/2007/06/upgradingmigrating-story-continues.html

  24. I migrated one of our Portal’s last night. Mostly things are working pretty well be we have come across one issue. When we edit or enter a new List item the columns (Fields) do not display in the sort order we have defined (Settings – List Settings – column ordering). (Column ordering within a view is working.)

  25. The Sort order issue is resolved. on Advanced Settings under List Settings there is a flag for “Allow Management of Content Type”. Change this to Yes

    Doing this step on all of our lists and document folders seemed to resolve a lot of issues.

    We have another problem though. My database won’t back up. I get transaction log backups but I’m getting this error when I try to do a full backup:

    System.Data.SqlClient.SqlError: The backup of full-text catalog ‘ix_STS_48GIDOC1_919767436’ is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online. Or BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. (Microsoft.SqlServer.Smo)

    48gidoc1 is our old sharepoint server. The SharePoint database on the new server is online and is functioning.

    I suspect some pointer didn’t get updated when I restored or renamed SQL objects during the migration process. If you have any ideas how to fix, please let me know.

  26. I deleted the full text catalog on the new sharepoint site and now I can create a backup.

  27. Travis said

    Has anyone tried to migrate a Sharepoint 2000 DB (on sql 2000) to Sharepoint 2007 (on sql 2005)? I tried the method mentioned above but when I try to attach the restored DB it says it contains user-defined schema and the db must be empty before it can be used.

  28. Tahir said

    Hey Farhan,

    I came across the migration of a site collection from SP 2003 to MOSS 2007 in July 2009 and your this post made my life bit easy.
    Just dropped by to say Thanks :o)

    -Tahir

  29. Omar said

    Hi Farhan . First ,I want to say thanks for such a nice article , Second , since you know Shrepoint 2010 is all 64 bit we want MOSS 2007 on 64 bit server also . Does this method you write above will work fine to migrate our data bases from sharepoint 2003 on 32 bit sql 2000/2005 to our new MOSS Farm which will be all 64 bit using sql 2005 64 bit .
    Mostly people have Sharepoint 2003 on 32 bit and now its old and gone Microsoft is all 64 bit . What will be your advice in this matter of 32 bit and 64 bit also can this methid be used from sql 2000 to 2005
    Once again thanks

    • Farhan Faiz said

      Hi Umar,
      We have shifted from 32-bit to 64-bit MOSS server using database migration and worked fine. No idea for SQL.

  30. Phi Hoang said

    I’m following this method to migrate my SharePoint 2003 to MOSS 2007. I ran into this error: ”

    The pre-upgrade scan tool has not yet been run on this database SPContentDatabase Name=*_SITE Parent=SPDatabaseServiceInstance. You must run the pre-upgrade scan tool before you can continue with the upgrade process. Run the tool from the following path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\prescan.exe.

    below are the steps that I follow:

    1. deployed MOSS 2007 on a new servers (I have 3 servers, web, app, and database – SQL 2008).
    2. download the prescan utility
    3. copy the prescan utility to the existing SharePoint 2003 server (I have 2 servers, web and database – SQL 2000)
    4. run the prescan on the existing sharepoint 2003 server

    prescan.exe /c preupgradescanconfig.xml /all

    the Prescan ran successfully – no error.

    5. backup the *_Site content database from the existing server (SQL 2000) that has SharePoint 2003
    6. restore the *_site on the new server (SQL 2008) that has MOSS 2007
    7. Create a new root site in MOSS 2007 in the new server
    8. Remove the content database from the new root site
    9. Add the content database back to the restored database *_site from SharePoint 2003 that has restored in the new server

    I’ve got the error shown above “the Pre-upgade scan tool has not been run…”

    the question is how/where to run the prescan.exe. I can not run Prescan in the new servers with moss 2007 since it requires SharePoint 2003 services.

    Greatly appreciated for the help.

  31. Anand said

    hi
    If i restore my sps 2003 database backup to the my new noss2007 site then how i wil get my all document liabrary and look and feel.Please any one help me

  32. Peter said

    Thanks farhanfaiz, SharePoint 2003 works with a read-only SQL database!

  33. Daniel Christian said

    Hi Farhanfaiz,
    I first tried the gradual upgrade process and ran into several issues. I then tried this method of Database migration. The difference is remarkable!! The database migration steps are easier and the process is flawless. Thank you for taking the time to provide these steps.

    Now that the database is migrated I want to migrate the ‘look and feel’ of the v2.0 site.
    Any ideas or suggestions?
    There are no ‘unghosted’ pages in the v2.0 site.
    Thanks in advance

  34. Nagaraj said

    Hi this is nagaraj i have query regarding migration from wss 3.0 to moss 2007.
    1.wss 3.0 is 32 bit server migrate to moss 2007 32 bit server only?
    2.from moss 32 bit server to sharepoint 2010 server?
    beacuse in some forum authors says migration from wss3.0 to sharepoint 2010 is not possible need to workaround as wss 3.0 server to moss 2007 and from that to sharepoint 2010.
    my question is if i will migrate from wss 3.0 32 bit server to moss 2007 32 bit server and from that moss 2007 32 bit server to sharepoint 2010 is it migration works.please guide me how to start my work.

    • Farhan Faiz said

      nagaraj,

      I have never experience the upgrade path mentioned. As per my understanding, this should be do able. But then again, If you have enough time and resources to test thoroughly, go for it.
      I am a bit confuse regarding your statement of “migrate from wss 3.0 32 bit server to moss 2007 32 bit”. It should be “upgrade” not “migrate”?

      • Nagaraj said

        many thanks Farhan!

        Which is the best practice for upgrading i am trying backup from central administration and restoring to new environment

        i will follow your steps mentioned and let you know Farhan.

      • Farhan Faiz said

        Welcome.
        “Which is the best practice for upgrading” This is a tricky question. I am not sure regarding you current hardware / software scenario. A lot of questions need to be answered like new hardware platform? SharePoint environment is customized or not?
        What I recommend is please sort your requirement and see which is best suit you.

  35. Moon Fiske said

    Great write-up, I am normal visitor of one’s web site, maintain up the nice operate, and It is going to be a regular visitor for a long time.

  36. Rob Tenorio said

    Hello, I was looking at the posting above and everything looks so simple to make a migration happen. My scenario is a little different. I have a sharepoint front-end server that is running sharepoint 2003 portal server and WSS2.0 on server 2003 std R2 32 bit. My config and content databases were recently migrated to a server running Server 2008 R2 64 bit with SQL Server 2008 without a hitch. I now have a new server running Server 2008 R2 Std. with MOSS 2007 that I would like to have as my front-end server and decommision my current server 2003 front-end server. What can I do to get my new 2008 R2 server to recognize the config and content databases. Please help.

    • Farhan Faiz said

      As per my understand, you need to create a web application and attach the newly migrated database with the we application. I am not sure regarding config. database. Why you need to migrate it?

      • Rob Tenorio said

        Hello, I’m trying to undstand your question. I currently have a config database that supplies the links to the sharepoint sites and then I have a content database that holds all of the data for all sharepoint sites. Both of these databases were migrated over to SQL server 2008. Now I have to attach a new Sharepoint 2007 MOSS to these databases. What needs to be done to nmake this possible?

        Thanks for your time.
        Rob

      • Farhan Faiz said

        If I remember correctly, In database migration we move content db only. I am not sure why we need to move config db as well?

      • Rob Tenorio said

        We thought we had to move that over as well at the time of migration from a 2003 R2 32 bit server with SQL 2000 old machine to a Server 2008 R2 64 bit with SQL 2008 new machine. Anyway, could you tell me what the process is to get a new Server 2008 R2 front end sharepoint 2007 server to attach to a Server 2008 R2 database server with SQL server 2008 that currently is currently hosting the content database for a Server 2003 R2 32 bit Sharepoint 2003 portal server with WSS 2.0? I just want to upgrade to Sharepoint 2007 (MOSS) and eventually up to Sharepoint 2010 since there isn’t a straight upgrade path from Sharepoint 20003 to Sharepoint 2010.

        Thanks again for your time.

      • Farhan Faiz said

        We have three approaches. In Place / Gradual and DB Migration. I am not sure what is the current environment like how much customization? How many master pages / page layouts / content type / custom web parts and others.
        Just look at the pros and cons of each approach as per your current environment and future plans.
        Let me know if further assistance is desired.

  37. If I may interject to answer Rob Tenorio’s question, database is all that you need to migrate from 2003 to 2007 and to 2010. I have just completed the migration where I work at and am in the process of “cleaning up” some web parts. The only unghosted page on SharePoint portal we have was the active directory contact which was built by Bamboo.
    I followed Farhanfaiz’s steps down to the teeth for 2003 to 2007 using only the database. In 2007 I didn’t waste time “cleaning up”. For 2007 to 2010 migration, two blogs really, really, really helped me.

    The first one was written by Marc Charmois. Below is the link
    http://mosshowto.blogspot.com/2009/11/installing-sharepoint-2010-windows-2008.html

    The second blog specifically deals with ‘User Profile Synchronization’ which is a new Web Application that came out in 2010. This Web Application deals with creating three separate databases for User Profiles which confirm’s farhanfaiz’s statement that only the site database is needed for the migration.
    http://www.harbar.net/articles/sp2010ups.aspx

    Hopefully this helps. It certainly helped me!!

  38. Vandana said

    After migration my SharePoint 2007 site default.aspx page still looks like SharePoint 2003 page on some sites, but not all. Can you please help?

    • Farhan Faiz said

      Can you please make sure that pages are inheriting the same master page.

      • Vandana said

        The pages are inheriting the same master page. (default.master)

      • Farhan Faiz said

        If I remember correctly, we used to have an option to change the look and feel to MOSS 2007. It must be on “Site Settings” page.

      • Vandana said

        I can change the layout but Iam trying to figure out what caused this.

  39. Yetanother SPUser said

    Hi Farhan, taking a backup of SPS2003 content database was very time-consuming, so I tried a slightly altered approach for just this part. I detached the content database in SPS2003, copied the MDF and LDF files to MOSS2007-SQL and attached the database using the copied files. Then I added the content database in Central Administration which upgraded the database. Now I am trying to repeat this procedure again, but I got this error – “One or more full-text catalogs are used by this database. Do you want to locate the full-text catalogs? (Click No to skip attaching the full-text catalogs.)”. I am surprised this did not happen in the detach-copy-attach procedure I did the first time. What do I do at this point? Can I skip the full-text catalogs and recreate them somehow on MOSS 2007?

  40. Ashwin Raj said

    Farhan, your article is very insightful. Thanks for your effort in putting it together! 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.

  41. […] https://farhanfaiz.wordpress.com/2008/05/23/sharepoint-upgrade-database-migration/ […]

  42. Excellent post. I was checking constantly this blog and I’m impressed!
    Very useful information particularly the last part 🙂 I care for such information
    much. I was looking for this certain information for a very long time.
    Thank you and best of luck.

RSS feed for comments on this post · TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: