SQL Server 2014 Express LocalDB does not create automatic instance v12.0 - by Alex V. Ivanoff

Status : 


Sign in
to vote
ID 845278 Comments
Status Active Workarounds
Type Bug Repros 9
Opened 4/2/2014 8:35:56 AM
Access Restriction Public


According to MSDN (http://msdn.microsoft.com/en-us/library/hh510202(v=sql.120).aspx), SQL Server 2014 Express LocalDB must have automatic v12.0 instance.
Sign in to post a comment.
Posted by Maharjan on 9/30/2015 at 8:53 AM
worked for me.
Posted by Sethu Srinivasan on 10/3/2014 at 10:56 PM
SQL 2014's Local DB sample connection string:

Data Source=(localdb)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\mydb.mdf;Initial Catalog=mydb;Integrated Security=True;MultipleActiveResultSets=True"
Posted by Microsoft on 5/19/2014 at 11:45 PM
Hi, Thank you for your feedback. In SQL14, we moved away from the numbering/versioning for the automatic instance and named it "MSSQLLocalDB" instead of "v12.0". The name of the automatic instance in the SQL14 documentation for LocalDB at http://msdn.microsoft.com/en-us/library/hh510202(v=sql.120).aspx has been fixed. If you require an instance to be named "v12.0", you can create a named instance with that name.
Thanks & Regards, Pooja Harjani, Sr. Program Manager, SQL Server, Microsoft.
Posted by Keith Dorken on 5/7/2014 at 12:57 PM
Found the LocalDB Instance API documentation (http://technet.microsoft.com/en-us/library/hh234692.aspx)
Posted by Keith Dorken on 5/7/2014 at 12:54 PM
Is there a way to enumerate the automatic instance names available (if more than one version of LocalDB installed)? "SQLocalDB.exe info" command (SQL 2014 version) will show the uncreated automatic instance names.

I suspect the automatic instance names come from the LocalDB\Bin\SqlUserInstance.dll (the "InstanceAPIPath" defined in the Installed Version registry key for the LocalDB installation) using some API call (currently undocumented).
Posted by csmithhelena on 4/15/2014 at 2:14 PM
Oops. Didn't read the username so both comments by the same user. Ok, in that case, thank you mvermef for posting the workaround. Saved me some frustration. :)
Posted by csmithhelena on 4/15/2014 at 2:14 PM
Thank both of you so much for the workaround!
Posted by mvermef on 4/10/2014 at 7:55 AM
disregard configuration issue, work around does work.
Posted by mvermef on 4/10/2014 at 6:50 AM
I am seeing this as well there is no default instance v12.0, creating it causes problems related to not being able to run against it due to it already existing error. Not sure if this has to do with the db trying to "attach" at was created using localdb v11 (aka Sql Server Express 2012 localdb). Suggested workarounds aren't solution causes more grief.

using connectionString = "Server=(LocalDB)\v12.0; Integrated Security=true;AttachDbFileName=|DataDirectory|\Data\somedb.mdf;MultipleActiveResultSets=True;" does not work now.

prior to this

connectionString="Server=(LocalDB)\v11.0; Integrated Security=true;AttachDbFileName=|DataDirectory|\Data\somedb.mdf;MultipleActiveResultSets=True;" worked just fine but wanted to move to the latest version.

This will play havoc for those that are running against LocalDB with attaching dbs at run time using said connectionstring. also noticed when it created the default instance it didn't create it in the v12.0 folder but in the Instances folder as root and named it MSSQLLocalDB but you couldn't connect to it.