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.
Related
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 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
Were I work we are currently using visual studio 2008 because 2010 did not include the bids stuff, I have now been asked to test out whether 2012 is any better so we have a virtual machine that I've been allowed to work on and we've got visual studio 2012 and 2012 integration services installed on it.
I tried to open one of our solutions which has various report projects in it. When I do this I get a one way upgrade option which I chose and then I get the following:
Projectname.rptproj: The application which this project type is based on was not found. Please try this link for further information: link
This link doesn't work properly and I can't seem to find very much on this for visual studio 2012 am I missing something here? Thanks in advance for any help.
Microsoft has recently released the tools necessary to open and create .rptproj projects in VS2012: Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012
According to this, it appears that you have to install the client tools for VS2012 (from the SQL2012 installer) in order to get the BIDS bits. Incidentally, installing VS2012 client tools will apparently update both VS2010 and VS2012.
I have Visual Studio 2010 and BizTalk Server 2010.
I need to uninstall BizTalk.
Is it possible to continue to use Visual Studio for BizTalk development?
If so, what do I have to do?
From BizTalk Server 2010 Microsoft made it completely free for development and testing purpose. Only BizTalk Server is free, not the dependant components like Visual Studio and SQL. SQL Express is not supported (http://blogs.digitaldeposit.net/saravana/post/2009/06/01/BizTalk-Server-with-SQLEXPRESS.aspx) .
You also need to keep in mind, you can use BizTalk Server with your MSDN subscription for development and testing purpose. Check it out.
You cannot totally uninstall BizTalk and continue to develop for BizTalk in Visual Studio, because completely uninstalling BizTalk will remove the Developer Tools and SDK. If you want to remove the BizTalk Server components, you can do that:
In your Control Panel, select Programs and Features or (if your settings are organized by category) select Uninstall a program.
Double-click on Microsoft BizTalk Server 2010 Developer Edition (assuming that the version and edition installed).
The Microsoft BizTalk Server 2010 Installation Wizard will open up.
Ensure that the Modify radio button is selected and press the Next button.
On the Component Installation page, uncheck all of the available components except for Developer Tools and SDK. Then press the Next button.
On the Summary page, select Install to proceed with the features removal.
I didn't know there is a free version of BizTalk.
nonnb's comment helped to resolve my license issue.
This doesn't seem to make sense to me - if you need to continue developing Biztalk projects, it will make life difficult without a local Biztalk (BizTalk dev edition is free and you can use SQL Express if you like). The Biztalk Deployment Framework (biztalkdeployment.codeplex.com/discussions) might assist with deploying to a remote server. – nonnb 2 days ago
I have Database project which I'm unable to load in VS2008 and I have SQL Server 2008 Express edition installed on my machine..
I get following error message, when I try to load
Database projects require a connection
to a local instance of Microsoft SQL
Server 2005 for design-time
validation. To perform this operation,
you must open the Tools menu, click
Options and specify an instance of SQL
Server 2005 that is running and to
which you can connect in the Database
Tools, Design-time Validation Database
property page. When that is corrected,
you must then refresh or reload the
database project.
Any suggestions/update to solve this issue?
You don't mention if you have VS2008 SP1 installed, but this is a requirement for SQL Server 2008 support in Visual Studio (KB956139)
Did you verify your instance name is correct? Tools > Options > Database Tools > Data Connections -> SQL server instance name: SQLEXPRESS (or the name you chose during install)
Does your instance accept remote connections? (mine always does, not sure if this is required) (Source)
I know this is an old thread, but...
Were you able to get this combination working? Visual Studio 2008 with SQL Server Express 2008? I had the same issue that no matter what I entered into the instance fields in the Tools->Options->Database Tools boxes, it said I did not have them entered.
From what I could find on the interwebs, everything indicated that SQL Server Express 2008 should work with Visual Studio 2008 as long as you have the SP1 installed. I tried reinstalling SP1, but received the same error - "no instance specified".
So I downloaded and installed SQL Express 2005 x64 and specified a new instance name, SQLEXPRESS2005. Then I plugged that into Visual Studio 2008's settings and it worked right away.