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
Related
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.
I am working on a project where I will be provisioned a SQL Server 2017 database server. However, the only version of SQL Server Management Studio available to me is 2008R2. I could request a newer version but this may take 1-2 months before it is finally installed on my machine.
Am I going to run into compatibility issues? Are there any database settings in SQL Server 2017 I would need to set in order to use this?
I am pretty unfamiliar with the MS suite of database tools so sorry for my ignorance in this! Thanks
In response to comments:
I have a managed system so I am not able to install or run software that has not been "approved". I have tried the portable version of VS Code but that did not work for me. I am going through the process of requests SSMS 2017 but like I said in the question this will not be available for 1-2 months. In the meantime will SSMS 2008 work?
As unlikely as this may be, I happen to have two, and only two, versions of SSMS installed on my machine; 2008R2 and 2017. I'm in the midst of an upgrade project.
I opened SSMS 2008R2 and was to connect to and generally poke around on a SQL Server 2017 server and the related databases. I didn't do anything too complicated (a few SELECT statments & an UPDATE), but they worked. The objects I expected to be visible were visible. And I didn't have to do anything to make it work. It just worked.
Mostly.
Except that every time I right clicked on a table, an error box opened with this message:
Index was outside the bounds of the array. (Microsoft.SqlServer.Smo)
But if I hit the OK button, the box cleared and the desired right click menu opened and functioned. That will get irritating, but if you poke around in the Options menu, there might be a way to make it stop. I invested no minutes trying to do that.
At the very least, you should be able to work while you're waiting for your upgrade.
For what it's worth, I work for a government contractor and have the same level of security constraints you do, so I feel your pain.
Another approach is to run sqlcmd, which would have been installed with SQL Server 2008R2. I was able to connect from sqlcmd to a SQL Server 2017 Docker container (external/internal ports 1433). I did not encounter any errors/warnings when creating a database and table, and running some light queries.
Interestingly, I was unable to connect to the same server using SSMS 2008R2. Perhaps the protocol used or the security required (e.g., TLS 1.2) for the underlying connection was different. Clearly it works based on Eric Brandt's results.
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've got SCCM 2012 R2 installed at a client with SQL Server 2012 SP1 installed in evaluation mode (as the client could not find their install key). I've heard that SQL Server licensing is included with System Center these days, but when the client (a smaller education institution) accesses their licensing, they see a large list of SQL Server versions listed, but every version says 'This version of the product does not require a key'.
Now I'm concerned, because leaving the installation in Evaluation mode will mean that SQL Server will fold up shop and not open after 180 days. Is there some special mechanism that bypasses licensing for SQL Server when ConfigMgr is installed? Why do I not see any valid license keys for SQL Server on the clients Software Assurance / Education licensing page?
Did I use the wrong version of SQL Server?
I found the answer, for anyone else stuck in the same problem.
If you use the ISO that you download from your volume license page, the SQL Server ISO should include the 'free SCCM' license baked in.
However, if you try to run this installer side-by-side on a server with a pre-existing install, SQL Server Setup will detect the other instance of SQL and not actually display the key. It will instead revert to displaying the 'Choose Evaluation or enter key screen'.
I found a way around though, wrote it up here: SCCM's SQL Stuck in Eval mode? How to fix!
In summary: download the SQL Server ISO found in the Volume License Center under System Center 2012 Configuration Manager, and run the installer on a clean server. This time you'll be able to see the pre-filled key, copy it and use this as your upgrade key using SQL Edition Upgrade from the SQL Setup. You'll get a warning stating 'Unsupported Upgrade Path' since the evaluation mode defaults to Enterprise, and the 'free' key is for Standard only, but it will still work.
I installed the Evaluation Edition of SQL Server 2012 and it has expired. I uninstalled the trial, rebooted, and installed the Developer Edition. It said it installed successfully; however, when I open SQL Server Management Studio it won't open and I get the message:
Evaluation period has expired.
You need to completely remove all SQL Server components from the machine when the trial has expired. Just removing the engine leaves other timebombs in place, as you've found out. So you will need to:
uninstall Developer edition
completely uninstall any and all remaining SQL Server-related things in Control Panel / Programs and Features
re-install Developer Edition
I posted a pretty lengthy blog post about this process, as it can get pretty messy and not everything can be removed gracefully from Control Panel (at least that was my experience with 2008 R2).
Basically you may need to run the following command...
msiexec /x "{GUID}"
...for every SQL Server-related GUID you find in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
See the post for a lot more details (just remember that GUIDs, and names that contain the version, changed between 2008 R2 and 2012, so don't take everything on-screen literally):
https://sqlblog.org/2010/10/25/fun-with-software-uninstalling-sql-server-2008-r2-evaluation-edition