Activity overview
Latest activity by MDJ
I replied a bit too quickly.
Looking at the LinkedDatabases.xml file I think I see the problem.
I actually have multiple instances for the DBs in question. Each has a slightly different value for ServerAndInstanceName.
A few examples:
<computer name>LOCALDB#05AC19B8
<computer name>LOCALDB#F0CCDDFC
<computer name>LOCALDB#315412F2
My guess is that the SQL instance name changes when the LocalDB server starts / restarts.
I normally sleep or hibernate my machine so the instance name wouldn't change unless it was actually shut down.
My actual instance name is a human readable name ("v11.0"). I also tested with an instance name of "UserTest" and LocalDB still returns the LOCALDB#XXXXXXXX instance name from SELECT SERVERPROPERTY('InstanceName'). I connect to them using the format "(localdb)<instance name>" (localdb)UserTest so I'm not sure why the actual instance name is the non human readable name.
I am not sure if there is anything you can about it at this point, that is part of how you track the DB instance (rightfully so). I may switch to SQL express as I do not think it behaves like this. / comments
I replied a bit too quickly.
Looking at the LinkedDatabases.xml file I think I see the problem.
I actually have multiple instances for the DBs in question. Each has a slightly different value for ...
A bit more information.
I cannot manually reproduce this issue by killing the SSMS process.
It has happened once when SSMS crashed for an unknown reason while not working within SQL Source Control.
It has also happened numerous times when my machine has restarted (unexpectedly) while I was away (maybe caused by my corporate IT upgrade policy but probably not as they usually occur in the evenings).
I will check out the LinkedDatabases.xml file the next time it happens and report back.
Thanks for the attention.
-Mark j / comments
A bit more information.
I cannot manually reproduce this issue by killing the SSMS process.
It has happened once when SSMS crashed for an unknown reason while not working within SQL Source Control....
LocalDB DB linking lost when Management Studio crashes?
We are evaluating SQL Source Control and I am testing it using some DBs created in localDB (v11.0).
So far everything works great and I have moved on to some more advanced use cases for our develop...