SQL Developer Edition Question

Question

SQL Developer Edition Question

Gabriel P

SSCarpal Tunnel

Points: 4289
More actions
July 2, 2013 at 10:23 am

#275716

Is it possible to restrict SQL Developer edition to only allow features in Standard edition? Our production environment is Standard Edition, and we are considering using Dev Edition in our dev environment due to the licensing, but we want to make sure whatever breaks in prod due to editions restrictions will break in dev.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323504 More actions · Answer 1

no, but the features differences all really have to do with a lot of advanced things, that would never come up in basic development; they come up more along the lines support, like max memory/processor, high availability features, auditing features, and maintenance and support.

take a peek here, and see if any of the Standard items columns are things you think you'd be using during development.

http://msdn.microsoft.com/en-us/library/cc645993.aspx

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Gabriel P SSCarpal Tunnel Points: 4289 More actions · Answer 2

Lowell (7/2/2013)
no, but the features differences all really have to do with a lot of advanced things, that would never come up in basic development; they come up more along the lines support, like max memory/processor, high availability features, auditing features, and maintenance and support.
take a peek here, and see if any of the Standard items columns are things you think you'd be using during development.
http://msdn.microsoft.com/en-us/library/cc645993.aspx

I work with a lot of developers that like to test the limits of things. It wouldn't surprise me if someone tried to use something like data compression

TheSQLGuru SSC Guru Points: 134017 More actions · Answer 3

Lowell (7/2/2013)
no, but the features differences all really have to do with a lot of advanced things, that would never come up in basic development; they come up more along the lines support, like max memory/processor, high availability features, auditing features, and maintenance and support.
take a peek here, and see if any of the Standard items columns are things you think you'd be using during development.
http://msdn.microsoft.com/en-us/library/cc645993.aspx

Not all of the things that come along with Enterprise/Developer edition are things a developer needs to "develop" (star join optimizations for example). Others they may not know are not available in std ed. (partitioned tables). Some are administrative yet important (online index rebuild, TDE). Others no one uses anyway (MDS, DQS). 😎

I too think it would be nice to have a Dev edition that doesn't expose non-EE-only features, but we don't have that. So it is up to the OP to school the team on what isn't usable in production.

Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service

Elliott Whitlow SSC Guru Points: 102296 More actions · Answer 4

Gabriel P (7/2/2013)
I work with a lot of developers that like to test the limits of things. It wouldn't surprise me if someone tried to use something like data compression

Then set policy not to use the features, if they do they need to understand there are no circumstances that an upgrade to enterprise will be allowed. So when stuff breaks in testing it will be their problem to fix it. In other words more work for them and the likelihood of pushing project deadlines. That usually help police people..

CEWII

Sean Pearce SSCoach Points: 15999 More actions · Answer 5

You can use a DMV on your dev databases to check if Enterprise features are in use.

SELECT * FROM sys.dm_db_persisted_sku_features

The SQL Guy @ blogspot[/url]

@SeanPearceSQL

About Me[/url]

TomThomson SSC Guru Points: 104773 More actions · Answer 6

Make sure that QA system is standard edition. Make sure that the development test system on which development integrates the various parts is standard edition.

Machines that developers develop on can be development edition: tell the developers they are not permitted to use EE features; after a few builds fail as soon as they get into integration and/or thrown out by QA they will obey the rule.

Tom