Today I try to create a connection on a new PC and such an error takes off. enter image description here

What could be the problem?

Closed due to the fact that off-topic participants cheops , Vladimir Martyanov , aleksandr barakin , Denis , pavel Nov 28 Nov '16 at 11:44 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reasons:

  • "The question is caused by a problem that is no longer reproduced or typed . Although similar questions may be relevant on this site, solving this question is unlikely to help future visitors. You can usually avoid similar questions by writing and researching a minimum program to reproduce the problem before publishing the question. " - Denis, pavel
  • “Questions asking for help with debugging (“ why does this code not work? ”) Should include the desired behavior, a specific problem or error, and a minimum code for playing it right in the question . Questions without an explicit description of the problem are useless for other visitors. See How to create minimal, self-sufficient and reproducible example . " - Vladimir Martyanov, aleksandr barakin
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • Well, as it is written there, what could be the problem - Anatol
  • It seems that there must be some kind of supplement in order for localdb to work. - Qwertiy
  • one
    if sql 2014 - try this: (localdb)\mssqllocaldb - Ruslan_K
  • @Ruslan_K thanks. - cruim

1 answer 1

This is a common problem for those who read the examples that were written before VS 2015. Since VS 2015, Microsoft has changed the agreement for the name MSSQL LocalDB.

When I use VS 2012 I use:

 (localdb)\v11.0 

For VS 2015:

 (localdb)\MSSQLLocalDB 

You can also see the available names for your machine by clicking on the menu at the top View -> SQL Server Object Explorer .

enter image description here