During cluster maintenance of SQL Server 2005, the following problem occurs:
When the resource group is on one node, log on to the database with SA and view the attributes of the user database from management studio. This is normal, but when the resource group is transferred to another node, log on to the database with SA and view the attributes of the user database from management studio. the following error is reported:
Title: Microsoft SQL Server Management Studio
------------------------------
The request dialog box cannot be displayed.
------------------------------
Other information:
The request dialog box cannot be displayed. (Sqlmgmt)
------------------------------
The property owner cannot be used for Database "XXXX ". This object may not have this attribute or cannot be retrieved due to insufficient access permissions. (Microsoft. sqlserver. SMO)
The first possible cause is the permission, but it is already a SA user. It should not be a direct cause.
It seems to be a problem with the user database owner,
After a rough comparison, the owner_sid of the user database does not exist in SYS. syslogins. It is estimated that the owner of the user database may be a local user.
Then, move the Resource Group to a normal node and open the attributes of the user database. The result is as follows:
Naturally, the owner is the local administrator. Because the owner is a local user, after switching the resource group, the owner cannot be found on another node, and an error is reported.
The solution is simple, that is, to change the owner to a user that can be found on both nodes. Execute the following statement and change the owner to sa.
ExecSp_changedbowner'Sa'