none
SQL2012 or 2016

    Question

  • I prepared new SQL2012 by request from the top...

    The server is planned to serve all new apps coming in near future.

    I mentioned from the very beginning that SQL2016 is the way to go...

    Some people are skeptical. I have a last chance to push SQL 2016. All what I read pointing that this is a right decision.

    Could there be problems in case we'll need to transfer/merge DBs from an existent SQL2008?

    I think that even we can expect some issues, it will be the same as having SQL2012.

    So, is SQL2016 is the right choice for new SQL deployment?

    Please "killer" pros :). I want to persuade the staff...


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, February 16, 2017 12:43 PM

Answers

All replies

  • Hello Miles,

    - newer versions have longer support time then older (logical, isn't it?)
    - new features like JSON support
    - Since SP1 for 2016: Enterprise-level In-Memory technology support also in Standard and Express Edition (in 2012/2014: Only Enterprise)


    Olaf Helper

    [ Blog] [ Xing] [ MVP]


    • Edited by Olaf HelperMVP Thursday, February 16, 2017 12:49 PM
    • Proposed as answer by Hilary CotterMVP Thursday, February 16, 2017 1:45 PM
    • Marked as answer by pob579 Thursday, February 16, 2017 1:55 PM
    Thursday, February 16, 2017 12:48 PM
  • Regarding potential issues , yes it may happen, but firstly run Upgrade Advisor to minimize them 

    https://www.microsoft.com/en-us/download/details.aspx?id=48119


    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    • Marked as answer by pob579 Thursday, February 16, 2017 1:55 PM
    Thursday, February 16, 2017 1:01 PM
  • Olaf,

    so generally you are on "my side" for 2016. Correct? :)

    when you mention Express... do you mean Express instance in SQL 2016?

    Thanks.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, February 16, 2017 1:03 PM
  • For sure, new development (if budget permits) should start on SS2016

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    • Marked as answer by pob579 Thursday, February 16, 2017 1:56 PM
    Thursday, February 16, 2017 1:04 PM
  • Hi,

    There's also SQL 2014 among the possible choices.

    SQL 2014 is very close to SQL 2012, but will give you 2 extra years of support (which is an important factor, because SQL 2012 is already at 50% of his support life).

    • Marked as answer by pob579 Thursday, February 16, 2017 1:56 PM
    Thursday, February 16, 2017 1:04 PM
  • Sure I checked EOL for 2012 and it is one of the factors why I recommend 2016...

    Thanks for your answers.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, February 16, 2017 1:15 PM
  • > Regarding potential issues , yes it may happen, but firstly run Upgrade Advisor to minimize them 

    https://www.microsoft.com/en-us/download/details.aspx?id=48119

    I spoke to the first vendor that will install the app on separate server and he confirmed no issues with SQL2016.

    He has a small (150MB) DB on current SQL 2008.

    General question:

    could SQL2012 be more beneficial for reducing migration problems from SQL2008 than SQL2016?

    I think that old DBs on 2008 will have the same problems (if any) regardless the future SQL - 2012 or 2016.

    Thanks.


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, February 16, 2017 1:42 PM
  • Yes, I mean the free (but limited) Express Edition of SQL Server 2016.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Marked as answer by pob579 Thursday, February 16, 2017 2:22 PM
    Thursday, February 16, 2017 2:13 PM
  • I want to say a special thanks :) to Uri, he suggested to run Upgrade Wizard for finding the potential compatibility problems.

    I did download the tool now called Data Migration Assistant (Upgrade Advisor is depreciated).

    Installed in seconds on the server in the same subnet were SQL 2008 runs.

    Impressive!...

    The server on which I am running the tool has only 1 virtual core, so it stays about 100%.

    I checked the target SQL... no impact the proc is on 3 %. So will leave the tool run.

    I checked all DBs for assessment (30). So looks like it will take a while. The machine I am running the tool is sleeping for most of the time.

    Hope I will get full info needed for migration to 2016.

    Thanks to all!


    --- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

    Thursday, February 16, 2017 7:28 PM