20 likes | 52 Vues
If the corresponding production server is running an Enterprise Edition, the development server will be mimicking the production as Developer Edition is exactly same as Enterprise – the only difference is the faith-based license agreement – no difference in code
E N D
SAVE LICENSING COST BY DOWNGRADING SQL ON YOUR TEST/QA SERVERS TO A DEVELOPER EDITION I have encountered many shops running either Enterprise or Standard Edition of SQL on Test/QA servers, squandering their money unnecessarily. The reason behind this is that SQL licensing has become difficult to comprehend just like our tax code. It would be prudent to downgrade the SQL Edition to a Developer Edition on all development /QA servers. However, be aware of few minor caveats: If the corresponding production server is running an Enterprise Edition, the development server will be mimicking the production as Developer Edition is exactly same as Enterprise – the only difference is the faith-based license agreement – no difference in code Even if the corresponding production SQL is running a Standard Edition and want the development server to mimic the production, it should be acceptable to use Developer edition on the Development/QA server as the Standard Edition has subset of features available in Developer Edition. The caveat here is that if Developers make use of Enterprise features on a development machine with Developer Edition and try to promote the code to production, the promotion may fail/cause problems If you have MSDN subscription, Developer edition should be free. If not, you just need to pay a $50 Developer Edition license fee per developer (This is NOT per server and each developer license can be used across any number of systems, all you need to pay is $50 X # of developers) To read more, please visit Satish Kartan's blog where he has shared more details on this. Also read: DEPLOYING YOUR SQL SCRIPTS AGAINST THE INTENDED SQL INSTANCE – By Satish Kartan