none
SQL 2012 migration to SQL 2016 RRS feed

  • Question

  • I have a customer running Windows 2008 R2 + SQL 2012 - running SAGE 300 software for inventory/billing etc.

    I would like to migrate them to Windows 2016 + SQL 2016 by purchasing a 2nd server & i would like to turn on Active Directory services. Two questions

    1.  What would be the best way to handle migration of licenses?- I'm assuming they have to buy licenses for Windows 2016 ( I am thinking of spinning up two VM instances) will SQL 2012 work fine under Windows Server 2016, or can i migrate existing Sql 2012 licenses to a new SQL instance of 2016 on the new server?

    2. Should I keep AD services separate from SQL?

    Appreciate any guidance from you guys. 

    thx

    Monday, February 5, 2018 9:14 PM

All replies

  • - SQL Server 2012 runs fine on Windows Server 2016.

    - If you want to use SQL Server 2016 you will have to buy licenses for that.  They don't upgrade version to version.

    - AD should be separate.  You should not have SQL Server running on a domain controller.

    - Windows Server 2016 licenses will be required as well.

    Monday, February 5, 2018 9:28 PM
  • Hi Syd C,

    >> will SQL 2012 work fine under Windows Server 2016

    According to this KB article, SQL Server can work fine under Windows Server 2016. However, make sure that you check known setup issues when you install SQL Server 2012 on Windows Server 2016. For example, Windows Server 2016 includes the .NET Framework 4.6. However, some SQL Server 2012 components like SQL Server 2012 Database Engine and Replication Service depend on the .NET Framework 3.5. Thus we recommend that you enable the .NET 3.5 Framework before migrating SQL Server 2012. For detailed information, please refer to the KB article.

    >> What would be the best way to handle migration of licenses?

    What is your output of SELECT @@VERSION? For licensing issue, you can take the licensing changes part of this link as reference. And for detailed information about the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.

    >> Should I keep AD services separate from SQL?

    Yes. It is not recommended to install SQL Server on a domain controller. First, there are specific security restrictions when running SQL Server in this configuration. Second, SQL Server performance may be degraded considering the resource demands of a domain controller. Furthermore, SQL Server is not supported on a read-only domain controller. Setup will normally fail. Even if you find methods to work around the problem with setup, SQL Server is not supported on a read-only domain controller. In addition, SQL Server failover clustering is not supported to install on a domain controller. For detailed information, please refer to You may encounter problems when installing SQL Server on a domain controller.

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

    Regards,

    Hannah


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" 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 MSDNFSF@microsoft.com.



    • Edited by Hannah Yu Tuesday, February 6, 2018 5:04 AM
    • Proposed as answer by Hannah Yu Monday, February 12, 2018 10:07 AM
    Tuesday, February 6, 2018 4:52 AM