September 25, 2016 at 4:48 pm
Hello,
I've got SQL Server Management Studio 2016, Visual Studio 2015, and SQL Server Data Tools installed on my computer. I'm told that all I need in order for localdb\projectsv12 to show up as an option of database engines to connect to in SSMS is to install Visual Studio and SQL Server Data Tools. I have those installed, but when I launch SSMS and go to select my server name, it only shows .\SQLEXPRESS. If I select <browse for more> I don't see localdb\projectsv12 under Database Engine or anywhere else.
What do I have to do to get localdb\projectsv12 to show up in SSMS as a database engine I can connect to?
Thank you.
September 25, 2016 at 5:32 pm
Well, you can at least connect to it from SSDT.
Choose Tools/SQL Server/New Query and then expand the 'local' node to select the connection you are interested in.
When I did this and ran
SELECT @@SERVERNAME
I got some nonsense back (machine name\LOCALDB#90ACA499).
So I tried connecting to that in SSMS, but the connection was unsuccessful (received a generic 'cannot connect to ...' error).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
September 26, 2016 at 7:20 pm
Phil Parkin (9/25/2016)
Well, you can at least connect to it from SSDT.Choose Tools/SQL Server/New Query and then expand the 'local' node to select the connection you are interested in.
When I did this and ran
SELECT @@SERVERNAME
I got some nonsense back (machine name\LOCALDB#90ACA499).
So I tried connecting to that in SSMS, but the connection was unsuccessful (received a generic 'cannot connect to ...' error).
Yes, going through VS, I can see ProjectV13 (still different from ProjectV12). How can I see this in SSMS?
October 10, 2016 at 12:48 pm
You can put in "(localdb)\ProjectsV13" in the Server Name field in SSMS.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply