none
is developer incompatible with windows 10?

    Question

  • Hi. I got a memo from our asset group today asking if I could give up my 2008 and 2012 developer versions of sql because of projected compatibility issues with windows 10 ( icurrently have windows 7 enterprise on my local).   I didn't even know how to answer them but did report I'm currently using  the 2012 product to 1) prototype something new locally, 2) use ssms for various development and analysis efforts across a variety of sql environments. 

    I guess my questions are 1) is 2012 developer really incompatible with windows 10?  in what respect?  2) if we run 2012 enterprise currently in production what alternatives might I consider for the best enterprise experience on my local?  3) we may be migrating tro sql 2016 in the next 6 mos.  Does this trigger any ideas in the community and wouldn't 2016's developer product also be incompatible with windows 10?

    • Moved by Tom Phillips Friday, January 27, 2017 6:50 PM Setup question
    Friday, January 27, 2017 2:53 PM

Answers

  • Please see:

    https://support.microsoft.com/en-us/help/2681562/using-sql-server-in-windows-8-and-later-versions-of-windows-operating-system

    • Marked as answer by db042190 Friday, January 27, 2017 6:13 PM
    Friday, January 27, 2017 2:55 PM
  • There is no difference between "editions" and OS requirements.  All editions would have the same problems.

    You need to install the current Service Pack to make it compatible.

    • Marked as answer by db042190 Friday, January 27, 2017 6:14 PM
    Friday, January 27, 2017 6:04 PM

All replies

  • Please see:

    https://support.microsoft.com/en-us/help/2681562/using-sql-server-in-windows-8-and-later-versions-of-windows-operating-system

    • Marked as answer by db042190 Friday, January 27, 2017 6:13 PM
    Friday, January 27, 2017 2:55 PM
  • thx.  a lot of info there.  my question is more from a "developer edition" perspective.  On the surface it appears your link suggests certain service packs when it comes to compatibility issues between sql 2012 and os's.  But otherwise they would be the same issues whether I had developer or any other version of sql installed.

    and 2008 just isn't compatible period.

    and if sql 2016 beats windows 10 to our desktops, nothing to worry about as 2016 is compatible out of the box.

    I've already asked our asset group if service pack 2 will be an option in sql 2012 if win 10 beats sql 2016 to our desktops.

    • Edited by db042190 Friday, January 27, 2017 4:02 PM after taking a closer look at the article
    Friday, January 27, 2017 3:06 PM
  • There is no difference between "editions" and OS requirements.  All editions would have the same problems.

    You need to install the current Service Pack to make it compatible.

    • Marked as answer by db042190 Friday, January 27, 2017 6:14 PM
    Friday, January 27, 2017 6:04 PM