SQL In-place Upgrade over 2005 on Dev ?

  • For testing, should I be able to do an "In-Place" upgrade from SQL 2005 to 2016 ?? Or is that too big a jump ?

    This is only for testing purposes. Production will be a new build from scratch.

  • homebrew01 (11/18/2016)


    For testing, should I be able to do an "In-Place" upgrade from SQL 2005 to 2016 ?? Or is that too big a jump ?

    This is only for testing purposes. Production will be a new build from scratch.

    Please check this page. As you will see, there is no direct upgrade path from 2005 to 2016.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • This was removed by the editor as SPAM

  • JasonClark (11/21/2016)


    Yes you can do 'In place upgrade'

    No, he can't. There's no in-place upgrade option for SQL 2005 to SQL 2016. See the link that Phil posted.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • This was removed by the editor as SPAM

  • JasonClark (11/22/2016)


    You check on this link:

    https://msdn.microsoft.com/en-in/library/ms143393.aspx%5B/quote%5D

    Sure (that's the same link Phil provided). First paragraph:

    You can upgrade from SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014.

    Not 2005.

    And then further down:

    In SQL Server 2016, you will be able to do the following:

    Attach a SQL Server 2005 database (mdf/ldf files) to SQL Server 2016 instance of database engine.

    Restore a SQL Server 2005 database to SQL Server 2016 instance of database engine from a backup.

    So no in-place upgrade from SQL 2005 to SQL 2016. Side-by-side may work (though the OS is likely to be the problem there) or a new server and then restore/attach the SQL 2005 DB, but not an in-place, which is what Homebrew was asking about.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • There are plenty of people who have shown that in-place upgrade from SQL2005 to SQL2016 is not possible, but even if it was why would you want to do it?

    The most recent OS the SQL2005 can work with is Windows 2008 R2. SQL2016 can be installed on this OS but Windows 2016 has many new features that SQL2016 can take advantage of. By using an old OS you would be restricting the capabilities of SQL2016.

    IMHO it is far better to plan to build a new virtual guest and build your test system on that.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply