Here, I’m trying to share knowledge about Day to Day Issues while working with SQL Server and their quick resolution.
order lexapro online canada Issue 1: Not able to access Database Properties
Error : Property Owner is not available for Database. The Property may not exist for the object or may not be retrievable due to insufficient access rights.
The Error comes when there is no owner of the database. If you run the command “ enter sp_helpdb <Affected_Datababase_Name>”, the “owner” property would show a NULL value. This issue can happen if the owner of the database is dropped from the Security Logins of the SQL Server.
To fix this issue, you can run following command against the affected database:
go sp_changedbowner 'new_login_name '
From SQL Server 2014, sp_changedbowner has been Deprecated and the alternate is as below :
Alter Authorization on Database::Database_name to Login_name
Issue 2: WMI Error while opening SQL Server Configuration Manager
Error: Cannot connect to WMI provider. You do not have permission or the server is unreachable.
This problem occurs when we have installed both 32 bit version and 64 bit version of SQL Server on same Windows Machine and when we uninstall an instance of SQL Server, WMI provider is also removed.The 32-bit instance and the 64-bit instance of SQL Server share the same WMI configuration file. This file is located in the %programfiles(x86)% folder.
To Resolve this issue, we need to locate the file “Sqlmgmproviderxpsp2up.mof” which is present at the
"%programfiles(x86)%\Microsoft SQL Server\number\Shared folder"
The value of number depends on the version of SQL Server
|Microsoft SQL Server 2012||110|
|Microsoft SQL Server 2008 R2||100|
|Microsoft SQL Server 2008||100|
|Microsoft SQL Server 2005||90|
Then, from Command Prompt we need to run below command.