Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Migrating CRM 4.0 SQL 2005 x86 to 2011 SQL 2008 R2 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am going to migrate CRM 4.0 all-in-one server with SQL 2005 x86 to a brand new CRM 2011 based on a two server configuration CRM + SQL 2008 R2 both joined to a different domain. On the "Microsoft Dynamics CRM Installing Guide" at "Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions", "Migrate by using a new instance of SQL Server" paragraph is written:

    "This procedure is useful when the Microsoft Dynamics CRM 4.0 deployment needs to remain available while Microsoft Dynamics CRM Server 2011 is installed (phase 1). Then, the Microsoft Dynamics CRM 4.0 deployment can be taken offline while the organization database is imported and upgraded into the new Microsoft Dynamics CRM 2011 deployment (phase 2).

    1.     If the configuration (MSCRM_CONFIG) and organization databases were maintained by a version of SQL Server that is not Microsoft SQL Server 2008 64-bit edition, upgrade the server or restore the databases to a supported version of SQL Server."

    This may be wrong because of is not possible to upgrade to 2008 64-bit edition on a x86 Windows Server. So what about point 1.??

    Thank you all for help

    Monday, August 27, 2012 3:48 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    I think what they are getting at is if you need to do a migration while still having your current system available during the upgrade/migration process you can create a new instance or installation of your current SQL Server version (probably SQL Server 2005) and backup/restore the CRM databases to the new instance/installation. When the CRM 2011 import organization process is started, it is to be pointed at the new instance/installation rather than your current production CRM 4.0 database (keeping it available longer).  Needless to say this doesn't actually prevent changes from being made to the current production 4.0 database while the 2011 import is happening. 

    Jason Lattimer

    Monday, August 27, 2012 5:45 PM
    Moderator