About this question
Is it dangerous to have dev environment with a Developer Edition and Live with Standard Edition, are the binaries different ?
Is it dangerous to have dev environment with a Developer Edition and Live with Standard Edition, are the binaries different ?
Log in to share your answer and help other learners.
Log in to answerBest Answer · By JanBask MS SQL Server Expert
Answered on Apr 24, 2021
No, it isn't dangerous, but it depends on which version of SQL Server you are talking about, what parts you are using (just the DB engine?, SSIS?, SSRS?, ...) and your level of aversion to the small risk. Developer edition is essentially Enterprise edition under a different licence. The problems you could hit are that some features might not be enabled in your production, standard edition, installation that are present in your development environment.
If you are using SQL Server 2016sp1 or above then this is unlikely to be a problem at all: almost everything is available to all editions. If you are using an older version then there might be differences to watch out for. For instance table level data compression was not supported outside enterprise (and developer) editions before 2016sp1 (including the original release of SQL Server 2016). The risk here being that one of your devs may make use of a feature that is not enabled in production. To see which features this affects, check MS's editions documentation: 2012, 2014, 2016, 2017. The risk here is small, and can be mitigated with care.
You could also go the other way: if you don't specifically need greater feature set and your dev environments don't have the data size to need more RAM than it will make use of, make your devs use Express instances then you know they won't use anything that won't be present when you deploy to Standard!
The differences beyond features between the editions and licensing options are how much RAM and how many CPUs/cores are supported. Unlike feature differences this will not cause your code to fall over because things are missing in production that are present in development, but it might cause performance differences. So again, the risk here is small. The same editions comparison pages listed above include this information also.
In any case, even if you use Developer edition for general dev, I would recommend using Standard edition in your Test environment because you want Test to be as close to Production as possible. Furthermore, matching versions and service pack levels, even if you don't match editions, is strongly recommended where possible.
SQL server developer vs express: MS SQL Server primarily stores and retrieves data from a database. It has different versions, like Enterprise, Standard, Web, etc., that support varying workloads. SQL Server Express, on the other hand, is a free database management system, which is a subset of SQL Server.
Free tutorials and interview questions from industry experts — learn the skill, then get ready to prove it.
Step-by-step SQL Server guides from industry experts
Common SQL Server interview questions, answered
Guides, tips and career advice on SQL Server from JanBask experts.
SQL Server Top 75 SSAS Interview Questions and Answers For Beginners & Experts
Prepare for your SSAS interview with our comprehensive guide featuring 75 top SQL Server Analysis Services interview questions…
SQL Server How to Become a SQL Database Administrator?
How to become a sql database administrator In 2025, discover what these professionals do, explore how much they earn and learn…
SQL Server OLAP vs OLTP: Key Differences, Architectures, Performance & Real-World Examples
Compare OLTP vs OLAP with clear definitions, architecture diagrams, real-world examples, and FAQs. Learn when to use each system…
SQL Server 70+ Most Asked SSIS Interview Questions for Freshers & Experienced
Prepare for your next SQL Server Integration Services (SSIS) interview with our top 70+ SSIS interview questions and answers.…