Trying to connect to a server/database on SMSS

Question

I am trying to connect to a third party database (Elmhurst) to edit the data contained within it, however I am getting the following error message whenever I try to connect to the database.

"The database DesignSAP2012Desktop is not accessible. (ObjectExplorer).

Details:

===================================

The database DesignSAP2012Desktop is not accessible. (ObjectExplorer)

---

Program Location:

at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DatabaseNavigableItem.get_CanGetChildren()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)

I've used the software for this function in the past however I didn't set it up myself and I'm a beginner with the software. If anyone can help me please explain it to me in simplistic terms.

Thanks.

Answer 1

The database DesignSAP2012Desktop is not accessible

As the message says, the DB is not accessible, e.g. because it is in recovery mode.
Connect with SSMS to SQL Server + "master2 database and check the state of the DB.

select name, state_desc
from sys.databases

Answer 2

Hi @Ben Westall ,

This may be a permission issue, perhaps this user login does not have the relevant permission to manage the database.
You can login with sa and expand Security>Login, right click on the username you need and then properties

click User Mapping and select the DB you want the user to access and then you can try connecting with the newly checked user.

Answer 3

No...that is not a right solution..that is not working

Answer 4

I was experiencing this same issue and finally figured out what happened. I restored a database and had to recreate the users. Login XYZ already existed, so I added XYZ to the restored database. Somehow though, those the login XYZ didn't seem to connect to the user XYZ. I deleted the database user XYZ, and then remapped the server login XYZ to that database, added proper schemas and then it worked again. Hope this helps.