Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Developer Edition Question


SQL Developer Edition Question

Author
Message
Gabriel P
Gabriel P
SSC Veteran
SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)

Group: General Forum Members
Points: 254 Visits: 943
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.
Lowell
Lowell
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14957 Visits: 38958
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
Gabriel P
SSC Veteran
SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)SSC Veteran (254 reputation)

Group: General Forum Members
Points: 254 Visits: 943
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
TheSQLGuru
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 5957 Visits: 8312
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). Cool

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 at GMail
Elliott Whitlow
Elliott Whitlow
SSCertifiable
SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)SSCertifiable (6.2K reputation)

Group: General Forum Members
Points: 6208 Visits: 5314
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
Sean Pearce
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1170 Visits: 3432
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

@SeanPearceSQL

About Me
TomThomson
TomThomson
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10707 Visits: 12008
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

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search