I have written an addin for my company using a local database. I am now in the stage of deploying it to other users using a setup so I can set the prerequisites. So far so good.
The issue I am having is that for some reason the database requires SQL Server 2016 LocalDB to be installed. Other users already have SQL Server 2014 Express LocalDB. In the prerequisites of the setup I put 2016, but for some reason the download is not functioning. It gives an error on the download (hresult 2146697203 in the log file). I read somewhere that there is no redistributable avialabe for 2016 and 2017. So I tried it with 2019. This is downloading and installing, but my database is not working. It wants 2016 for some reason.
My question(s):
Is it possible to change the local database to 2019 or 2014 Express?
Or do I need another bootstrapper for 2016?
Or is there another option I am missing/overlooking?
I have recently installed SSMS 17 and SQL Server from this link: SSM Studio,
and I also installed SQL Server Express from the official site.
As on SSMS download page there are two downloads available SSM Studio 17.6 and 17.6 upgraded packages so I installed both. And now I am confused a bit because in SSMS I see two database engines SQLEXPRESS and SQLEXPRESS01 although it only connects to RAO-HAMMAS-PC as you can see here in the screenshot:
Also I see two instances of SSMS 17.6 in programs and features window - see this screenshot
and both have same version but different size. Please help me if I have duplicate installed SSMS ?
And just one more thing SQL Server keeps running in background even if I am not using it. So can I stop it somehow? And only use it when I am developing?
I have installed a Evaluation 180 days version of SQL Server 2012 from the official website of Microsoft, on a Windows Server 2012 R2 (with gui). At the end of the installation in the Installation center, everything passed and succedeed but when I quit the program, I don't have any way to execute SQL Server from a graphical interface. I can see MS instances created, services running but how can I get a GUI to work with SQL Server?
With the newer version of SQL Servers, the SQL Server Management Studio (the GUI) is a separate install and you will need to install it separately to the database engine installation (which is what you have done). You can download SSMS from here https://www.microsoft.com/en-us/download/details.aspx?id=29062. The page contains a lot of different download components, make sure you check the appropriate install and click download.
ENU\x64\SQLManagementStudio_x64_ENU.exe if you want the 64bit installation of SQL Management Studio
ENU\x86\SQLManagementStudio_x86_ENU.exe for the 32bit version.
you Need to Install SSMS
SQL Server Management Studio (SSMS) is a tool to manage and administer SQL Server and SQL Database.
SSMS is offered free of charge by Microsoft.
I performed what I thought was an upgrade from SQL Server Express 2012 to 2014 by running the 64-bit executable. Everything seemed to be working fine during installation as it recognized my existing server instance (2012) which I presumed would be upgraded to 2014.
However, when I try to restore a 2014 DB from my web host, I get the following error:
The database was backed up on a server running version 12.00.2000.
That version is incompatible with this server, which is running
version 11.00.5343. Either restore the database on a server that
supports the backup, or use a backup that is compatible with this
server.
I definitely have 2014 installed, but when I view my instance from inside SMS 2014 it looks to still be running on SQL version 11.xxx which I presume is 2012 (the name of the instance is the same as it was when I was running 2012).
Did I do something wrong during the installation? How do I upgrade my instance to 2014 so that I can restore my DB locally?
downloadsqlserverexpress.com helps to find the correct download of SQL Server Express from MS Download Center. You need the one that contains the SQL Server Engine, not just Management Studio.
sqlserverbuilds.blogspot.com.au has a full list of SQL Server versions and builds.
Using it we can see that you are running Management Studio 2014 (build 12.0.2000.0), but you are connecting to SQL Server 2012 engine (build 11.0.5343).
Maybe you now have two engines running (both 2012 and 2014). You can check the list of running processes and verify if two instances of sqlservr.exe are running.
It should be possible to upgrade the engine in place by installing 2014 on top of 2012. I don't know why it didn't happen in your case. You could have chosen to install only Management Studio even if you had a full installer.
One long, but sure way to clean up would be to uninstall everything related to SQL Server and install 2014 again. Make proper backups of databases at first, of course.
When I try to install a new instance of SQL Server 2008 Express on a development machine with SQL 2005 Express already up and running, the install validation fails because the "SQL 2005 Express tools" are installed and I'm told to remove them.
What exactly does that mean?
After reading this article:
http://www.asql.biz/Articoli/SQLX08/Art1_5.aspx
I uninstalled the 2005 version of the SQL Management Studio but received the same error from the 2008 installer during my follow-up attempt.
Updates
1) Uninstalled the SQL 2005 Management Studio only. Received the same error from the 2008 install.
2) Removed all SQL 2005 common components. Received the same error from the 2008 install.
3) Installed the shared components from the SQL 2008 installation program. Received the same error from the 2008 install when trying to install the new SQL 2008 instance.
4) Uninstalled SQL 2008 components, rebooted, re-installed SQL 2005 Management Studio from installation media, rebooted, un-installed SQL 2005 Workstation Components from Control Panel, re-booted.
Installation of SQL 2008 is now proceeding as it should.
Seems likely that if I'd re-booted after update 2 above things would have gone more smoothly. :-(
Although you should have no problem running a 2005 instance of the database engine beside a 2008 instance, The tools are installed into a shared directory, so you can't have two versions of the tools installed. Fortunately, the 2008 tools are backwards-compatible. As we speak, I'm using SSMS 2008 and Profiler 2008 to manage my 2005 Express instances. Works great.
Before installing the 2008 tools, you need to remove any and all "shared" components from 2005. Try going to your Add/Remove programs control panel, find Microsoft SQL Server 2005, and click "Change." Then choose "Workstation Components" and remove everything there (this will not remove your database engine).
I believe the 2008 installer also has an option to upgrade shared components only. You might try that. Good luck!
In my case even after uninstalling all 2005 related components it didn't worked. I had to resort to a brute force way and remove following registry keys
32 Bit OS: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
64 Bit OS: HKLM\Software\Wow6432Node\Microsoft\Microsoft SQL Server\90
I had to unistall the Workstation Components and SSMS Tools Pack (SSMS Tools Pack is an add-in for Microsoft SQL Server Management Studio (SSMS) including SSMS Express.)
Installation of SQL 2008 is now proceeding as it should.
The problem is that SQL 2008 MS has a bug where connecting to a remote server (say like a service provider collocation) it will always try to open the fist db in the list, and since the possibilities of been ur db the first on the list are really low, it will throw and error and fail to display the list of dbs... which using sql 2005 management studio it just works.
Wished I could use SQL 2008 MS, but looks like as far I connect to remote SQL 2005, SQL 2008 is out of the question on my dev machine :(
Just Remove the the Workstation Components from Add/Remove Programs - SQL Server 2005.
Removing Workstation Components, SQL Server 2008 installation goes well.
Simply remove the Microsoft SQL Server Management Studio Express 2005 from control panel
N.B. These notes are for SQL Server Express 2008 R2 (so Microsoft still haven't made this any easier). I also realise that I complicated things by installing 32-bit SQL Server Express 2005 and 64-bit SQL Server Express 2008.
I followed the steps by Josh Hinman above. Uninstalling the SQL Server Express 2005 "Workstation Components" was not enough. I required an uninstall of the 2005 Management Studio as well.
I also tried the Upgrade route that Josh Hinman suggested by clicking on the 'Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008'. This route never gave me the option of installing the components side-by-side it just went straight through the process of upgrading from 2005 to 2008. It completed successfully - but hadn't actually done anything. Thankfully though it hadn't harmed any existing database instances. So be warned trying that route.
If you currently have Red Gate SQL Toolbelt, you will need to unistall that too before continuing. Somehow it adds a reference to the 2005 version of the SQL Management Studio.
I'am trying to install SQL SERVER developer 2008 R2 alongside SQL SERVER 2005 EXPRESS,
i went to program features, clicked on unistall SQL SERVER 2005 EXPRESS, and only checked, WORKSTATION COMPONENTS, it unistalled: support files, sql mngmt studio
After that installation of sql 2008 r2 developer went ok....
Hopes this helps somebody
I also had to remove the SMSS before it would get past that step.