• Phil Parkin - Saturday, February 25, 2017 11:31 AM

    If you close and reopen SSMS, does it make any difference?

    Nope but imposing a default database on connection seems to have solved the issue???
    I chose to connect to a default database when opening solution explorer and that seemed to solve whatever the problem was.

    Never had that problem before...
    Weird