This really had me confused. I have used SSOE plenty in VS2012 and on my laptop that I just replaced, in VS2013. But on my new laptop and on my desktop, I can go through the motions of adding the (localdb)/v11 database to SSOE with no errors and still, nothing shows up under the SQL Server branch of the tree.
Finally I opened VS2012 to see if *it* would show my databases in SSOE. Instead I got a message that SQL Server Data Tools (SSDT) was out of date.
SSDT is an extension to Visual Studio 2012 which that team was releasing whenever they had updates to it.
But for VS2013, it’s just a part of the full IDE.
My out-of-date VS2012 SSDT was causing a conflict with the built in tools for VS2013. Go figure. But installing the October 2013 update to SSDT (you’ll find an update for VS2010 and for VS2012) fixed the problem. Now I can see my databases in SSOE in both version of visual studio.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!
3 thoughts on “Fix for VS2013 Not Showing Databases in SQL Server Object Explorer”
This unfortunately did not solve the problem for me (or perhaps only partially solved the problem); I also had to add a new server in VS 2013, using (localdb)\v11.0 instead of (localdb)\Projects. See here — http://stackoverflow.com/questions/20200162/ssdt-on-visual-studio-2012-broken-then-fixed-broken-again-also-broken-on-vs2013 — for more info.
Sorry I didn’t think to specify that step. You have to do it almost every time you are using the SQL Server Object Explorer after starting up VS2013 so in my mind, it wasn’t really part of the fix. But I’m glad you’ve pointed it out for next person who comes along and isn’t as used to having to do that step as I am. 🙂
I have just hit a brick wall (SqlGeometry in a table-valued parameter); so , as you have adviced us all, i turned to esql , and problem solved …