locked
moving all SharePoint databases to new SQL Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We’ve got a Windows Server 2003 64 Bit Standard Edition with SharePoint Server 2007 and SQL Server 2005 installed.

    I want to move all databases from the SharePoint Server to a Windows Server 2008 R2 Datacenter Cluster with SQL Server 2008 R2.
    The Microsoft article     Move all databases to a different database server     describes that the old and new server have to have the same OS and SQL Server Version.
    Is there a possibility to move the databases to the Cluster without migrating the SharePoint Server to Windows Server 2008?

    Friday, July 8, 2011 9:01 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    You challenge here is primarily around the configuration DB.  It is very easy to move SharePoint Content DB's.  The Config DB actually has some hard-coded references to it's underlying SQL Server.  You have 3 options to move this DB:

    1. Delete the farm and recreate it using the new SQL Server.  This isn't as bad as it sounds - but is work intensive
    2. Create a SQL Alias on SharePoint server and point the SharePoint server to connect to a different SQL server based on the same "name"
    3. Create the new SQL Server to have the exact same name as the current server.

    There is one last options which is more of a hybrid option:

    - leave the config DB on the current server and move all content DB's to the new cluster.

    I hope you find this helpful-

    Jeff DeVerter, MCSE
    Rackspace
    blog:http://www.social-point.com
    twitter: http://www.twitter.com/jdeverter


    Jeff DeVerter
    • Marked as answer by Markus Recktenwald Friday, July 8, 2011 9:40 AM
    • Edited by Mike Walsh FIN Saturday, July 9, 2011 6:55 AM Do NOT ask people to mark your post as an answer
    Friday, July 8, 2011 9:17 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You challenge here is primarily around the configuration DB.  It is very easy to move SharePoint Content DB's.  The Config DB actually has some hard-coded references to it's underlying SQL Server.  You have 3 options to move this DB:

    1. Delete the farm and recreate it using the new SQL Server.  This isn't as bad as it sounds - but is work intensive
    2. Create a SQL Alias on SharePoint server and point the SharePoint server to connect to a different SQL server based on the same "name"
    3. Create the new SQL Server to have the exact same name as the current server.

    There is one last options which is more of a hybrid option:

    - leave the config DB on the current server and move all content DB's to the new cluster.

    I hope you find this helpful-

    Jeff DeVerter, MCSE
    Rackspace
    blog:http://www.social-point.com
    twitter: http://www.twitter.com/jdeverter


    Jeff DeVerter
    • Marked as answer by Markus Recktenwald Friday, July 8, 2011 9:40 AM
    • Edited by Mike Walsh FIN Saturday, July 9, 2011 6:55 AM Do NOT ask people to mark your post as an answer
    Friday, July 8, 2011 9:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Jeff,

    Thanks for the quick reply. I will testing the first option,  If it doesn´t work, i will use the last option and move only the content DB´s.

     

    Markus Recktenwald

    Friday, July 8, 2011 9:40 AM