After installing Visual Studio 2017 with the SQL Server Data tools feature checked, I noticed LocalDB was not installed. How can I add SQL Server LocalDB 2016 to my Visual Studio 2017 installation? Did I miss a checkbox when installing VS2017, or is it simply not included with the installer? If so, how do I configure VS2017 so I can view and connect to my manually installed LocalDB database in Visual Studio's server browser?
It's automatically installed if .NET Desktop Development is checked.
You can check it in the Summary.
SQL Server Express 2016 LocalDB is in .NET desktop development. If you missed it to select while installing Visual Studio 2017, you can select and install it later.
To install SQL Server Express 2016 LocalDB, go to Start in your Windows OS, type Visual Studio Installer and run it. Then click Modify. It will open the Workloads selection screen where you can select .Net desktop development. .Net desktop development includes SQL Server Express 2016 LocalDB. After selecting, click Modify and you are done.
But although you select .NET desktop development, it may not install. Because SQL Server 2016 or later is not supported for many processors. To check this, visit Hardware and Software Requirements for Installing SQL Server If this is your case, then you have to depend on SQL Server Express 2014 LocalDB or previous.
To install SQL Server Express 2014 LocalDB manually, download the installer from Microsoft® SQL Server® 2014 Service Pack 2 (SP2) Express and install SQL Server Express 2014 LocalDB by running the installer.
To connect to LocalDB, open Server Explorer in Visual Studio, right-click on Data Connections-> Add Connection. Enter Server name: (localdb)\MSSQLLocalDB and Test Connection. If test is success, click OK and you are now connected.
It is a component under the .NET desktop development workload.
As others have pointed out, LocalDB is automatically included if you select certain workloads, such as Desktop or ASP.Net.
However, you may not want one of those workloads. You may just want to add LocalDB.
In the Visual Studio Installer, navigate away from the Workloads tab to the second tab (Individual components). Here, the individual items are listed alphabetically, and can be selected or deselected for installation:
New to the conversation, but wanted to share what I ran into because it may not be apparent that localdb was installed already. Here's another step you can take to verify.
I ran into this same issue and found out that I'd already installed localdb via desktop.
I was getting a connection string error and thought I did something wrong, but what I ended up doing is opening the SQL Server Object Explorer from within Visual Studio and sure enough, it was there.
Shortcut, Ctrl+\ & Ctrl+S, or View -> SQL Server Object Explorer.
If you choose
ASP.NET and web development
then the option
SQL Server Express 2016 LocalDB
will also be checked and installed.
I have the same issue here, I followed the accepted answer but I think nothing has been installed. I followed the installer, and everything was checked ever since I installed my Visual Studio 2017 Professional Edition:
After all successful installation, and tried to modify it again using the installer, it will show the that I need to download the same tools which I installed multiple times. In other words, I have the same window as my image I showed above even though I already installed and modified it several times. And LocalDb still is not yet installed.
So I directly downloaded it here, you can even choose your own version: SQL Server Express LocalDB
Then upon successful installation using the link above, I was now able to confirm that LocalDb has finally installed on my machine.
To query, run command prompt and input:
I know this is a little different that what is asked, but the symptom is similar so I'm posting this. I figured out what I was missing. I was following a tutorial on Pluralsight, Bethany's Pie Shop, "Building Your First ASP.NET Core 2.0 MVC Application VS 2017", and tried running the solution downloaded. I had a failed login message... I re-watched a couple of the videos. This is what I was missing. I needed (in VS) to go to View->other windows->PkgMgrConsole
- Make sure you've built the application (build solution at top of VS)
- in console at bottom.... add-migration InitialMigration
- in console.... update-database
- run program
The person asking this didn't say how he got to the point that he thought he didn't have localDb installed. I checked, and I had it installed, but it was giving me a failed login message when I tried running the program without these steps.
If you use Visual Studio Installer and select only .Net desktop development,it will uninstall all workloads you had before.
It's a lengthy process beware.
I have visual studio 2010 installed and working on my computer.
recently I have updated sql express 2008 to sql 2012. after visual studio prompted
"this server version is not supported. only servers up to Microsoft SQL
server 2008 are suported"
I have installed sql server data tools (from here https://msdn.microsoft.com/en-us/jj650014) to solve this problem, however unfortunately it keeps showing the message.
What am I doing wrong? How do I solve this?
Your best bet will be to install the latest version of SSDT from Microsoft. VS DB Projects stopped support with SQL 2008. SSDT for SQL 2010 stopped support w/ SQL 2012, I think. You don't need a license for the VS shell, though you might need to sign up w/ the MS developer program.
Go here for the SSDT blog: https://blogs.msdn.microsoft.com/ssdt/ You should see the most recent post or two pointing to the current release. This should support 2012+ without any issues. It will install the VS IDE if you don't have it installed.
FYI, the version you pointed to should work with SQL 2012, but you'd be better off using the latest version that is currently under active development. Ideally, the dacpac should be able to be used regardless of which version of SSDT you're using.
It might be worth checking to see what you're turning in. If you can turn in a script, it won't matter what version of SSDT you use. If you need to turn in the dacpac, you might have to double-check your install for SQL Express and SSDT to be sure they are the proper versions.
I am having a problem similar to this one. However, the only answer suggested there doesn't work for me.
Specifically I am trying to upgrade from VS2010 to VS2013. I have an oracle database project (.oradbproj file type) as part of our main solution and it isn't recognized in 2013. I have ODAC 11.2.0 installed on the computer and I also tried to fix the problem by re-installing it after I installed VS2013. So far, nothign has worked.
Any Ideas?
Edit, Additional information: I have noticed that I am also missing the "Oracle Database Project" project template. I believe this was added to VS2010 by the ODAC, but it is not appearing in VS2013.
The solution that I found is to install Oracle Developer Tools for Visual Studio v. 12c.
--Jacob
I have started to prefer SSDT to SQL Management studio. But suddenly when I needed it I could not find SQL Server Object Explorer in view menu.
Not sure who took it away, I recently pushed update-2 for visual studio.
I could not locate stand-alone version of SSDT for VS-2013
Can any one please save me from re-installing Visual Studio :-(
According to this blog post on MSDN SSDT is now an integrated part of VS:
Visual Studio 2013 - VS 2013 now has SQL Server tooling built in and
shipped as part of the core product. Database Projects, SQL tools
(such as schema compare & data compare), and the online experiences
through SSOX are all included with the RTM version. We have full
project and SSOX support in VS Express for Web and Express for Windows
Desktop, so we have discontinued our stand-alone integrated shell
offering.
When I looked at the Extensions and Updatesin VS2013 I had an update available for SQL Server Data Tools and when I clicked it I got a downloadable installer (SSDTsetup.exe) which might be what you are looking for.
The link that gave the download was this: go.microsoft.com/fwlink/?linkid=393521&clcid=0x409
I am installing Visual Studio 2010 Ultimate and I am doing a custom installation where I can choose the tools I want and install it in the preferred installation directory.
I am only in need of visual c++ and the graphics library. That's all i need as I am just starting to learn c/c++. Despite choosing just two tools, it installed SQL server compact and a bunch of other components which I didn't ask for. This is consuming a lot of disk space in the C: drive where Windows is installed. I need at least 5 GB of free space on the C: drive for future Windows update but now I am left with only 3 GB.
Question:
1)Why does visual studio install sql server along with the c/c++ compiler? And why did it occupy space in the directory which I didn't specify?
2) Is it safe to uninstall sql server and its components?
I am aware that .NET framework is necessary for visual studio to run.
SQL Server Compact is used internally by some Visual Studio components. I think InteliSense database is one of them, storing metadata information about projects in your solution (look for *.sdf files, those are SQL Server Compact databases). So I would definitely not advise you to uninstall SQL Server Compact.
The same is true for other SQL Server components installed by Visual Studio, although maybe to lesser degree. Visual Studio components using them may not be needed in your case, and if they are needed they should let you know by giving you the right error message. One component I wouldn't touch is SMO (SQL Server Management Objects).
If you installed SQL Server Express (not Compact) it is absolutely safe to get it uninstalled.
1) Why does visual studio install sql server along with the c/c++ compiler?
And why did it occupy space in the directory which I didn't specify?
It installs only Express version of Sql Server and it comes by default with intention that your application development will need Sql Server Express.
2) Is it safe to uninstall sql server and its components?
Yes, you can uninstall it if you don't need Sql Server.