Is it possible to upgrade SQL Server 2008 Enterprise Evaluation to Developer Version Or Express?
I we have some old Account software that uses SQL and the Tech that Migrated the Software used the Enterprise Evaluation Copy (Now Expired) and not the Express (Even though it would have been OK for this application).
We only need to use the software until the end on Jan 2018 so i wanted the most cost effective way of getting it back online.
I have tried an Edition upgrade to Express but it does not work the Upgrade wizard works but the SQL Server service with not start. Getting an Error 17051 which seems to lead to Trial Expired.
I can get hold of a Developer licence at a responsible price but wanted to Know if that would work prior to Purchase.
If anybody has had a similar problem would appreciate any help!
Related
A recent issue that occurred was identified by software engineering to be a result of installing SQL Server RTM instead of SQL Server Standard. I have done the obligatory google search to attempt to find a difference between release versions but may not know enough to know what I do not know about Microsoft SQL Server versioning. Is there anyone who has an official reference to Microsoft documentation that can explain the difference between an RTM version of MSFT SQL Server 2016 vs MSFT SQL Server 2016 standard?
Standard is one of the editions of SQL Server, with others being
Express (including Express LocalDB, Express with Advanced Services)
Web
Enterprise
Developer
etc.
RTM denotes the first/initial release-to-manufacturing release - a full, finished release (not a beta, not a release candidate - a full finished product). It is also the initial finished release - without any "service packs" or "cumulative updates" yet.
Those are two totally unrelated things ... you cannot get a difference between the two, since they denote two utterly unrelated facts about SQL Server
I'm currently looking at a SQL Server which was upgraded (by somebody else) from SQL 2008 R2 to 2012 last year. The database works fine, so apparently nobody noticed that a Standard Edition (SE) instance had been upgraded with Enterprise Evaluation Edition (EEE) media. The two database instances stayed as SE but the Management and Client Tools are EEE.
After 180 days the trial ran out and some things stopped working. I noticed these problems when I did a health check on the server and tracked the cause back to that upgrade (SQL Server's saved summary logs every time you even think about changing it are a great help figuring out what happened).
I now have the correct installation media and the SE license key. But I'm not sure how best to proceed. Just uninstall the existing tools and reinstall the correct ones? I've never run across a situation like this so any experience or suggestions gratefully accepted.
I tried it out on a test server with a similar setup and the answer does seem simply to be to uninstall via Windows, reinstall from the original media, and then service pack/CU/patch back to the right level.
Aha! -- this is probably it. On the very weekend I elected to set up the DNN site on Azure ... Web and Business versions are deprecated / retired. As of yesterday in fact, this is what is on Azure.
The ONLY 2 choices in SQL Server 2012 SSMS however, to import a data tier app are just Web and Business. Basic, Standard and Premium are not in the drop down in SSMS 2012.
So ... rather than just zap this question I'll put in another question within it. Is there an update to SSMS 2012? I ask because the database being migrated is 2012 so using SSMS 2014 may not work, if the option is to download this version of SSMS and use it.
Other than that ... here's what's already posted:
Note, the SQL Server database being migrated is 2012. DNN Version is 07.02.01 (367).
I'm following the steps in this blog link to migrate a DNN site to Azure: http://www.dnnsoftware.com/community-blog/cid/154975/moving-a-dnn-install-to-microsoft-azure-websites. The error I get is:
'web' is not a valid database version in this edition of SQL Server.
I have 2 choices in the import process 'Web' and 'Business', tried both and neither will work. There are a few other Stack Overflow questions on this but these are either not answered or the answers don't work.
I realize this is vague but it's simple enough: It doesn't work. :) The blog is followed to the letter. The .bacpac file is created with no errors. Importing the data tier step just results in the error that creating the target database on Azure failed for the above reason.
I have a support ticket in to Azure for this as well.
There has to be a simple, overlooked something -- a missing config step on setting up Azure. It could be the free trial doesn't cover this and I need to pay for something. That's fine ... just need to know what it is.
Who has run into this and actually, factually solved it?
My recommendation is always to use the latest SSMS version available, in order to have the latest updates supporting new Azure features like: full-text search support for Azure SQL Server v12, the long requested "Edit top 200 rows" working, the table designer, and a long etc.
Note that the latest SSMS release supports SQL Server 2016 through SQL Server 2005, so is going to work fine with your SQL Server 2012 database. On the SSMS June 2015 Preview, the following item was added:
Import/Export wizard support for new Azure SQL Database service tiers (Basic, Standard, Premium).
You can read more at https://msdn.microsoft.com/en-US/library/mt238290.aspx
https://support.microsoft.com/en-us/kb/3031047
For future reference. This hotfix should work on this problem.
That is because the valid database version could be basic or standard or premium. SSMS does not allow to choose it, therefore, the solution is to download the latest version of SSMS.
I was using SQL Sever 2012 Evaluation edition. As it was about to expire, we purchased a Standard edition license.
I was told that I don't need the lisence key as it was embedded in the ISO installation file. However, when trying to run the installation file, I get the message - There are no SQL Server instances or shared features that can be updated on this computer.
The reason for this is that the edition that I was trying to install was 2012 SP1, which is the version that I was already on.
When trying to do the upgrade using the Configuration manager and then choosing maintainance -> Upgrade, I get asked for the product key, which I don't have.
The advice from the Microsoft account manager was to let my product expire and then try the upgrade again. However after the product expired I still have exactly the same issue.
Any advice besides uninstalling SQL and reinstalling?
Thanks,
Niel
You should be able to run an 'Edition Upgrade' of an existing SQL Server instance, even on an expired evaluation, you can do it via the SQL Server setup from the Installation media, and SQL Server Installation Center, by clicking on 'Maintenance', then 'Edition Upgrade' and follow the rest of the installation from there.
The error message is generally caused by applying incorrect versions (patched up, language incorrect etc.) on an instance that is different. The 'Select features' page has a description message on the top right side of the page explaining what is ocurring. I'd suggest taking a look there first of all.
Please check this post, although it relates to 2008 R2, the error fix is the same in 2012 :-
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c82da968-bbfb-4803-a9b2-876776f033d6/there-are-no-sql-server-instances-or-shared-features-that-can-be-updated-on-this-computer?forum=sqlsetupandupgrade
This should have the answers that you need.
Regards,
Dave
I have updated my SQL Server 2008 R2 Evaluation Edition to Enterprise Edition a
couple of weeks ago. Service Pack 1 is also installed. Things were going good for a while . But when I run an SSIS package now, I get a Warning:
0x80000036: only 9 days left for evaluation.
can anyone help me out in resolving this issue?
It looks like your upgrade didn't go through smoothly. In 9 days your message will read "Integration Services evaluation period has expired. The package can only be executed in debug mode."
Why not try to change the edition again via the Edition Upgrade Wizard?
There is a good thread on MS Social (Bought SQL Server 2008 Developer Licence, How do I upgarde my Trial version with Licence version?) suggesting to...
Use the Edition Upgrade Wizard
Use a command line action to upgrade
Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=MSSQLSERVER /PID=<PID key for new edition>"
Contact the MS Licensing Team with questions directly (in the end you bought the product-that's what support is for ;-) )