SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Go from SQL 2008 R2 standard edition to Developer?


Go from SQL 2008 R2 standard edition to Developer?

Author
Message
Brian Kukowski
Brian Kukowski
Mr or Mrs. 500
Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)Mr or Mrs. 500 (599 reputation)

Group: General Forum Members
Points: 599 Visits: 1625
Is it possible to 'downgrade' SQL 2008 R2 from standard edition to Developer edition?

I'm working on developing a long-term SQL Server infrastructure for my company. We're evaluating using the Enterprise edition, but my bet at this point is that we'll go with Standard at least short-term. If, at some point in the future we decide to go to Enterprise, we'd want to (A) upgrade our production Standard installs to Enterprise, and (B) change our non-production installs to Developer to reduce licensing costs. (I'd be OK with the production environments having slightly less capabilities, since Developer is now equivalent to Data Center)

From what I've seen (http://msdn.microsoft.com/en-us/library/ms143393.aspx), it doesn't look like what I'd like to do is possible. Hoping someone knows otherwise. I'd like to avoid having to install SQL Server from scratch if we changed editions. Thanks....

Brian Kukowski

Brian Kukowski
UMG Developer
UMG Developer
SSCertifiable
SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)SSCertifiable (6.5K reputation)

Group: General Forum Members
Points: 6470 Visits: 2204
Brian Kukowski (4/4/2011)
If, at some point in the future we decide to go to Enterprise, we'd want to (A) upgrade our production Standard installs to Enterprise, and (B) change our non-production installs to Developer to reduce licensing costs.


From what I have seen Microsoft doesn't support that.

I would advise you to be careful about your use of the Developer edition, my understanding from talking to Microsoft is that nobody without a Developer edition license can access the server, or look at the reports created from it if it contains real/production data. i.e. you can't use it for QA/UA with real data if users accessing it, or the results from it, don't have developer licenses.

I would love to be wrong, as it would save us a bunch of money, but that is what Microsoft told me.
Jim Murphy
Jim Murphy
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2369 Visits: 1265
Yep. Piece of cake to do this. UMG has some good caution about the licensing differences and to be careful not to violate the agreement for using the Developer edition.

But on the technical side, I just did this about a week ago, if I can only remember exactly what I did. I remember just rerunning the installer (setup) from the Developer edition media and point it at your existing instance. Somewhere after specifying the existing instance, it'll ask you if you want to 'upgrade'. Upon choosing yes (including all related services like SSRS), it prompts for the key. I slapped in my dev edition key and it completed the upgrade. Checking my version showed the dev edition.

One of my employees needed to install R2 to do some development work but my only dev edition/MSDN license was on my own system, so I had him install the standard edition 6 month trial. Course, this was, um, 6 months ago. In the mean time, I bought another dev edition license (Amazon.com!) but didn't get around to reinstalling until the tools smacked him down one day last week.

Anyway, most of my trepidation was not wanting to point the installer at my instance, hoping for an earlier non-hosing option which would tell me if this path would even work in the first place. Once I ran through it as a last-ditch "I'm going to uninstall/reinstall next anyway" effort, I found that the installer handled it properly.

Jim

Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
mark.dba
mark.dba
Valued Member
Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)

Group: General Forum Members
Points: 71 Visits: 192
Solution proposed by previous post (Jim Murphy) doesn't work. Just tried it to downgrade SQL 2008 Enterprise to Developer.

Current system:
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)
10.0.5500.0, SP3, Enterprise Edition (64-bit)


It may work with additional steps, but it doesn't as mentioned in the post.

Mark
chris wood-205215
chris wood-205215
Valued Member
Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)Valued Member (66 reputation)

Group: General Forum Members
Points: 66 Visits: 216
Jim posted about standard to Developer, I expect Enterprise to Developer is another kettle of fish
Jared Karney
Jared Karney
One Orange Chip
One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)

Group: General Forum Members
Points: 29893 Visits: 3700
I can tell you from experience that there is no downgrade path. Even though DEV has all of the features of Enterprise, it is considered a downgrade and does not work.

Thanks,
Jared
PFE - Microsoft
SQL Know-It-All
How to post data/code on a forum to get the best help - Jeff Moden
tim.cloud
tim.cloud
SSC-Addicted
SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)

Group: General Forum Members
Points: 470 Visits: 349
I recently had to downgrade a server from Enterprise to Developer as we wanted to ensure the proper licensing compliance on a dev box.
What I did was:
1.) Clone the server using VMWare (all our dev servers are virtual, only production servers are physical).
2.) Rename the existing server "servername_old".
3.) Detach all the databases on the clone.
4.) Uninstall SQL Enterprise on the clone.
5.) Reboot.
6.) Install SQL Developer on the clone (we also had the "old" VM to use as a reference.)
7.) Attach all the databases.
8.) Script out the creation of the logins from the "old" VM.

So, in less than 2.5 hours (which included the time it took to create the clone) we solved a similar issue with a dev server.
tim.cloud
tim.cloud
SSC-Addicted
SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)SSC-Addicted (470 reputation)

Group: General Forum Members
Points: 470 Visits: 349
Also, it should be noted that Standard to Developer is no downgrade.
In terms of features, Developer is identical to Enterprise.
Jared Karney
Jared Karney
One Orange Chip
One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)

Group: General Forum Members
Points: 29893 Visits: 3700
tim.cloud (7/10/2012)
Also, it should be noted that Standard to Developer is no downgrade.
In terms of features, Developer is identical to Enterprise.
Maybe so in terms of features. However, it is considered a downgrade. I have called and spoken to MS people in this. Features do not determine an upgrade or downgrade. Ultimately, the company does.

Thanks,
Jared
PFE - Microsoft
SQL Know-It-All
How to post data/code on a forum to get the best help - Jeff Moden
mark.dba
mark.dba
Valued Member
Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)Valued Member (71 reputation)

Group: General Forum Members
Points: 71 Visits: 192
I have successfully downgraded about 20 servers in our environment. I am working on doing the same to the clustered ones too.

I tested cluster downgrade on a test cluster and it worked.

We had SQL Server 2008 Enterprise everywhere and had to downgrade in lower environments to SQL Server 2008 Developer.

The basics are this. Install Developer edition and look at the registry in Setup dir. Take those keys and copy them to Ent. server. You have to restart SQL Service for it to "know" it's now Developer edition.
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