#Exchange 2019 standard vs enterprise code

You also acknowledge and agree that we may modify this Agreement at any time, in our sole discretion and that all modifications to this Agreement will be effective immediately upon our posting of the modifications on the website, with or without notice to you. By accessing, browsing, or using this website, including any linked pages owned and operated by PSX or CS, or any partner thereof or any part of this website you acknowledge that you have read, understood, and agree to be bound by these Terms. The Terms constitute a legal agreement between you, PSX & CS and govern all use of this website, including all content, information, and services provided on the website. Furthermore, matching versions and service pack levels, even if you don't match editions, is strongly recommended where possible.Pakistan Stock Exchange (PSX), CS Solutions (Pvt) Limited and its affiliates (collectively, 'PSX & CS') provide this website to you, subject to these terms of use ('Terms'). 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. The same editions comparison pages listed above include this information also.

#Exchange 2019 standard vs enterprise code

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. The differences beyond features between the editions and licensing options are how much RAM and how many CPUs/cores are supported.

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 risk here is small, and can be mitigated with care. To see which features this affects, check MS's editions documentation: 2012, 2014, 2016, 2017.

The risk here being that one of your devs may make use of a feature that is not enabled in production. For instance table level data compression was not supported outside enterprise (and developer) editions before 2016sp1 (including the original release of SQL Server 2016). If you are using an older version then there might be differences to watch out for. 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. 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. ) and your level of aversion to the small risk.ĭeveloper edition is essentially Enterprise edition under a different licence. Mostly 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?.