Technical FAQs

Ask a Question

Unable to Open SQL Server Database Properties Window

Unable to open SQL Server Database properties window within SQL Management Studio. 
The following error is returned when you right-click on the database and select the properties option.

Cannot show requested dialog. (SqlMgmt) Property Owner is not available for Database 'ION_Network'.
This property may not exist for this object, or may not be retrievable due to insufficient access rights.

Microsoft SQL Sever

SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014

This error may appear due to the fact that there is no owner for this database.  Possibly the login has been deleted from
the SQL Server or if it is a windows or domain account then the account may have been removed from Active Directory. 
Also it may be possible that SQL Server cannot validate this account due to permission or connectivity issues with Active Directory.


*Warning: Irreparable database damage can occur. This procedure should only be performed by users familiar with SQL Server Management Studio. Databases should be backed up prior to performing this procedure.*

As it is not possible to use the interface to check the database properties, it cannot be seen if there is a database owner present for the
database, or if an owner is present, then what is the name of that account. To verify the owner of a database run the below query.

sp_helpdb [DBName];

Once it has been identified that there is no database owner or the login does not exist any more, the command below can be used to
change the database owner to a different account.

Use [DBName]
EXEC sp_changedbowner 'SA';

After running the above command, the properties of the database can now be opened without any error.  Instead of the 'SA' account
you can now choose any login which exists in the SQL Server instance and is valid.  However it is important to note that after sp_changedbowner
is executed, the new owner is known as the dbo user inside the database. The dbo has implied permissions to perform all activities in the database.
This allows the database owner to perform all operations inside the database including dropping the database itself.

This issue may not occur with all databases within the SQL Server instance. You may be able to open other databases properties
on same SQL Server instance without any errors.

** see attachment containing the SQL script text
Was this helpful?
What can we do to improve the information ?