cancel
Showing results for 
Search instead for 
Did you mean: 

Property Owner is not available for Database[...]

Former Member
0 Kudos

Hi,

I install ERP2005 under Windows 2003 with SQL 2005. Under this machine we have 2 SAP installations with 2 different database instances. When i try to connect through SQL management Studio to get the properties of one database i have the following error:

Property owner is not available for database[ERP]. And i can not connect to the database. The SAP systems are up and running with no problems.

I use windows authentication mode...

Do you have any idea how to correct this error?

Thanks in advance.

Thanasis

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

execute following on sql query

USE ERP

EXEC sp_changedbowner 'erp'

Former Member
0 Kudos

Dear kaushal malavia,

i use the script that you proposed me and i have the following error under sql query:

Msg 15110, Level 16, State 1, Line 1

The proposed new database owner is already a user or aliased in the database.

Do you have any other idea?

TP

Former Member
0 Kudos

Hi,

try to execute following query and share the result.

use ERP

EXEC sp_grantdbaccess 'erp'

EXEC sp_addrolemember 'db_owner', 'erp'

go

use master

EXEC sp_grantdbaccess 'erp'

EXEC sp_addrolemember 'db_owner', 'erp'

go

use msdb

EXEC sp_grantdbaccess 'erp'

EXEC sp_addrolemember 'db_owner', 'erp'

go

use model

EXEC sp_grantdbaccess 'erp'

EXEC sp_addrolemember 'db_owner', 'erp'

go

use tempdb

EXEC sp_grantdbaccess 'erp'

EXEC sp_addrolemember 'db_owner', 'erp'

use master

go

EXEC sp_addsrvrolemember 'erp', 'serveradmin'

EXEC sp_addsrvrolemember 'erp', 'dbcreator'

EXEC sp_addsrvrolemember 'erp', 'bulkadmin'

regards,

kaushal

clas_hortien
Active Contributor
0 Kudos

Hi,

use this script:

use ERP

exec sp_changedbowner 'sa'

Regards

Clas

Former Member
0 Kudos

Dear Clas,

Thank you for your answer. The problem solved. Do you have any idea how is this possible to happens in a system?

TP...

clas_hortien
Active Contributor
0 Kudos

Hi,

this can be happen, when you

- use a nt account to attach the database

- delete the nt account

The same can happen, if the current owner (nt account) cannot be verified against the AD.

You can see the used account in the property window of the database (right click -> properties).

The problem can be easily identified, when you click on Users in the database, If the dbo user / schema has no login assigned or is not visible, you are dealing with this problem.

Regards

Clas

Former Member
0 Kudos

Dear Clas,

Thank you for your answers...

Best regards,

Thanasis

Answers (0)