Issue 1In SQL Server Management Studio, you connect to an instance of SQL Server 2008 as a user who is not a member of the sysadmin fixed server role. When you try to expand the Databases node in Object Explorer, you receive the following error message:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
The server principal "<User>" is not able to access the database "<Database>" under the current security context. (Microsoft SQL Server, Error: 916)
Issue 2You have lots of database backups. In SQL Server Management Studio, it takes a long time to expand the Databases node in Object Explorer. Additionally, when you try to run a query that returns the following information from the backupset system table in the msdb database, the query takes a long time to run:
- The date of the last log backup
- The date of the last backup
- The date of the last differential backup
Issue 3When you run the sp_spaceused stored procedure to return the size of the current database and the space that is used by indexes, the sp_spaceused stored procedure takes a long time to run.
Cause 1When a user who is not an administrator tries to access some database properties, the user does not have permission to access some catalog views. Therefore, an exception occurs in the SQL Server Management Objects (SMO) enumerator.
Cause 2If you have lots of database backups, lots of rows exist in the backupset system table in the msdb database. SQL Server Management Studio runs a query against the backupset table when you to try to expand the Databases node in SQL Server Management Studio.
Article ID: 958760 - Last Review: Jun 2, 2009 - Revision: 1