none
sqlserver 2016 upgrade question

    Question

  • Hello everyone,

    Did anyone face difficulties with having SQL Server 2016 sp1 Dev edition in non prod (Dev, Staging, Preprod and UAT) instances and SQL Server 2016 sp1 standard edition in production?

    I know developer edition is on par with enterprise and sql server std has less features than ent but that's from a HA/DR and BI perspective. However from development perspective would there be any coding issues. 

    please share your thoughts.

    Thanks


    Wednesday, June 27, 2018 6:18 PM

All replies

  • <<Did anyone face difficulties with having SQL Server 2016 sp1 Dev edition in non prod (Dev, Staging, Preprod and <<<UAT) instances and SQL Server 2016 sp1 standard edition in production?

    No we have not. We had to tune some queries under new estimation coordinator ( db has been moved from SQL SERVER 2005)  and made it work smoothly 

     But there is SP2  has been already released, must install 

    Developer Edition as  you probably know  has same functional as EE but must be used in DEV  environment  

    What coding issues are you talking about?


    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

    Thursday, June 28, 2018 5:05 AM
    Moderator
  • Lot of people us this to save cost so you are not the one. And to be specific please let us know the exact issue

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Thursday, June 28, 2018 5:57 AM
    Moderator
  • Dev team should always keep in mind that they are working on DEV edition in non prod which is on par with EE where as prod is Standard Edition. So when they are developing or coding something they shdnt use any specific development feature that is available in DEV but not in Standard. Any such features that we shd be aware off or let them know upfront?

    Also I believe we should not restore a database from non prod to prod in this scenario per licensing standards. Is it true?

    Thursday, June 28, 2018 6:36 AM
  • I guess you are quite aware about the shortcoming :)

    You can by all means restore database from non prod to prod assuming your prod is licensed. The problem that may come is when you restore EE backup on standard and if you might have used any Ent feature it will fail to restore


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Thursday, June 28, 2018 7:30 AM
    Moderator
  • Hi sqldba_24,

     

    From your description, I understand that you'd like to know some difference between enterprise edition and standard edition in programmability.

     

    Advanced R integration, Advanced Python integration, Machine Learning Server (Standalone) and Polybase head node are supported in enterprise edition. However, they are not supported in standard edition. If in SQL Server Dev edition using the four features, there will occur problems when executing in standard edition. For more details, please refer to the document which compares features across all editions of SQL Server 2016. https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2016?view=sql-server-2017

     

    As for your second question, it seems about license. 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.

     

    Best Regards,

    Emily


    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


    Thursday, June 28, 2018 7:33 AM