none
Duplicate and Upgrade SQL Server

    Question

  • Hi, I have a question about the steps to duplicate and upgrade SQL server.

    Now, I have a windows 2008 32bit server and runs SQL server 2005 on it. Then I would like to build another server, which is windows 2012 64bit and runs SQL server 2008 on it. I need to duplicate everything from the first server to the second one and keep both of them running at the same time, such as reports and so on.

    What should I do? Any one knows the steps to finish this project?

    Appreciate it!

    Wednesday, April 19, 2017 9:53 PM

Answers

  • There is so much to migrate I would be tempted to clone the OS and then upgrade the OS and then SQL Server.

    If you want to migrate you need to migrate the following;

    1) databases

    2) logins

    3) extended stored procedures

    4) jobs

    5) proxies, certificates

    6) linked servers

    7) ole-db providers

    8) file system dependencies

    9) CLR assemblies

    10) replication components

    11) custom sysmessages

    12) alerts

    Tibor Karaszi has a list which is pretty definitive.

    http://www.karaszi.com/SQLServer/info_moving_database.asp

    • Marked as answer by yxzhou624 Monday, May 1, 2017 8:06 PM
    Thursday, April 20, 2017 12:46 AM
  • I have a windows 2008 32bit server ... is windows 2012 64bit 

    Please note: A cross-platform 32 bit => 64 bit upgrade is not supported, see Supported Version and Edition Upgrades => Unsupported Scenarios

    And running a 32 bit SQL Server on a 64 bit OS won't perform well. Better make a fresh Windows OS and SQL Server installation then a migration; may some more efforts for installation, but finally it will work better and causes less issues at the end.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]


    • Proposed as answer by Davy_Wang Thursday, April 20, 2017 10:09 AM
    • Edited by Olaf HelperMVP Thursday, April 20, 2017 10:19 AM
    • Marked as answer by yxzhou624 Monday, May 1, 2017 8:06 PM
    Thursday, April 20, 2017 3:11 AM

All replies

  • There is so much to migrate I would be tempted to clone the OS and then upgrade the OS and then SQL Server.

    If you want to migrate you need to migrate the following;

    1) databases

    2) logins

    3) extended stored procedures

    4) jobs

    5) proxies, certificates

    6) linked servers

    7) ole-db providers

    8) file system dependencies

    9) CLR assemblies

    10) replication components

    11) custom sysmessages

    12) alerts

    Tibor Karaszi has a list which is pretty definitive.

    http://www.karaszi.com/SQLServer/info_moving_database.asp

    • Marked as answer by yxzhou624 Monday, May 1, 2017 8:06 PM
    Thursday, April 20, 2017 12:46 AM
  • Also run the upgrade advisor to find any upgrade blockers.  I take it you know that SQL 2008 is no longer supported by Microsoft  - right?
    Thursday, April 20, 2017 12:47 AM
  • I have a windows 2008 32bit server ... is windows 2012 64bit 

    Please note: A cross-platform 32 bit => 64 bit upgrade is not supported, see Supported Version and Edition Upgrades => Unsupported Scenarios

    And running a 32 bit SQL Server on a 64 bit OS won't perform well. Better make a fresh Windows OS and SQL Server installation then a migration; may some more efforts for installation, but finally it will work better and causes less issues at the end.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]


    • Proposed as answer by Davy_Wang Thursday, April 20, 2017 10:09 AM
    • Edited by Olaf HelperMVP Thursday, April 20, 2017 10:19 AM
    • Marked as answer by yxzhou624 Monday, May 1, 2017 8:06 PM
    Thursday, April 20, 2017 3:11 AM
  • Hi yxzhou624,

    Any update on the issue, was the issue resolved? If the issue has been resolved, please mark the corresponding replies as answer as it would benefit others when they are reading this thread. If not, could you please provide more information so we can have a better understanding about the issue?

    If you have any other questions, please let me know.

    Regards,
    Davy

    MSDN Community Support<br/> Please remember to click &quot;Mark as Answer&quot; the responses that resolved your issue, and to click &quot;Unmark as Answer&quot; if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact <a href="mailto:MSDNFSF@microsoft.com">MSDNFSF@microsoft.com</a>.

    Wednesday, April 26, 2017 6:12 AM