Cannot view DB properties

Upgraded from SQL 2000 to SQL 2005. I am using Domain User with admin rights
to view the DB properties and its failing with "Property Owner is not
available for Database '[DB_name]'. This property may not exist for this
object, or may not be retrievable due to insufficient access rights.
(Microsoft.SqlServer.Smo)"
I was able to view the properties of the same database using same domain
user when we were in SQL 2000.
How to solve this issue? Any input is appreciated..
ThanksIT (IT@.discussions.microsoft.com) writes:
> Upgraded from SQL 2000 to SQL 2005. I am using Domain User with admin
> rights to view the DB properties and its failing with "Property Owner is
> not available for Database '[DB_name]'. This property may not exist fo
r
> this object, or may not be retrievable due to insufficient access
> rights. (Microsoft.SqlServer.Smo)"
> I was able to view the properties of the same database using same domain
> user when we were in SQL 2000.
> How to solve this issue? Any input is appreciated..
How did you upgrade? Did you upgrade the server in place, to did you
reattach the database?
It sounds as the latter. The SID for the database user, does not seem to
match any login on the server. Use
ALTER AUTHORIZATION ON DATABASE:db TO [domain\user]
and if necessary, create a login for the domain user first.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I did In-Place Upgrade, I have like 20 databases and when I checked using
sp_helpdb for all databases, found NULL for 5 databases.
I followed the command
ALTER AUTHORIZATION ON DATABASE::database_name TO sa
Failed with:
Msg 15110, Level 16, State 1, Line 1
The proposed new database owner is already a user or aliased in the database
.
Any other workarounds? Is this a Bug...in SQL 2005...
"Erland Sommarskog" wrote:

> IT (IT@.discussions.microsoft.com) writes:
> How did you upgrade? Did you upgrade the server in place, to did you
> reattach the database?
> It sounds as the latter. The SID for the database user, does not seem to
> match any login on the server. Use
> ALTER AUTHORIZATION ON DATABASE:db TO [domain\user]
> and if necessary, create a login for the domain user first.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>|||IT
Sorry, I don't understand , what do you mean by "In-Place Upgrade"?
I just did testing and it worked fine.
1) BACKUP DATABASE command on SQL Server 2000
2) RESTORE DATABASE command on SQL Server 2005
3) Drop user in the database after restoring
4) CREATE LOGIN on SQL Server 2005
5) CREATE USER in the database and mapped it to the new created LOGIN
If it does not help, please privide with steps you did so far.
"IT" <IT@.discussions.microsoft.com> wrote in message
news:A8BF2B36-4223-49A6-948B-E5097FC52082@.microsoft.com...[vbcol=seagreen]
>I did In-Place Upgrade, I have like 20 databases and when I checked using
> sp_helpdb for all databases, found NULL for 5 databases.
> I followed the command
> ALTER AUTHORIZATION ON DATABASE::database_name TO sa
> Failed with:
> Msg 15110, Level 16, State 1, Line 1
> The proposed new database owner is already a user or aliased in the
> database.
>
> Any other workarounds? Is this a Bug...in SQL 2005...
>
> "Erland Sommarskog" wrote:
>|||Here are the steps I followed:
# Ran the setup and upgraded the existing SQL Server 8.00.818 to SQL Server
2005.
# I have like 20 databases and only for 5 databases I noticed that database
owner was NULL after the UPgraded finished successfully.
# I checked that by using sp_helpdb...IN the OWNER filed found NULL for
those 5 databases.
# Ran sp_changedbowner 'sa' and it updated the OWNER to SA
# If I want to change the owner to any existing user in the database it
gives me
following error.
Msg 15110, Level 16, State 1, Line 1
The proposed new database owner is already a user or aliased in the
database.
I can only change the Owner to sa and for any other USER if throws me the
error I mentioned above.My question here is , Even though I upgraded the
existing instance of 2000 to 2005, why is that only for 5 databases I am
seeing this kind of behaviour.
Every thing was fine when it was in sql 2000.I was able to change the DB
Owner...
Thanks
"Uri Dimant" wrote:

> IT
> Sorry, I don't understand , what do you mean by "In-Place Upgrade"?
> I just did testing and it worked fine.
> 1) BACKUP DATABASE command on SQL Server 2000
> 2) RESTORE DATABASE command on SQL Server 2005
> 3) Drop user in the database after restoring
> 4) CREATE LOGIN on SQL Server 2005
> 5) CREATE USER in the database and mapped it to the new created LOGIN
>
> If it does not help, please privide with steps you did so far.
>
>
> "IT" <IT@.discussions.microsoft.com> wrote in message
> news:A8BF2B36-4223-49A6-948B-E5097FC52082@.microsoft.com...
>
>|||Sounds like a phantom user situation which is causing your error to be
thrown.
Check out http://sta.c64.org/sqlprg.html
And download http://sta.c64.org/sqlprg/fixusers.zip
Before you run the script be sure and read what it does.
Good luck to ya.
IT wrote:[vbcol=seagreen]
> Here are the steps I followed:
> # Ran the setup and upgraded the existing SQL Server 8.00.818 to SQL Serve
r
> 2005.
> # I have like 20 databases and only for 5 databases I noticed that databas
e
> owner was NULL after the UPgraded finished successfully.
> # I checked that by using sp_helpdb...IN the OWNER filed found NULL for
> those 5 databases.
> # Ran sp_changedbowner 'sa' and it updated the OWNER to SA
> # If I want to change the owner to any existing user in the database it
> gives me
> following error.
> Msg 15110, Level 16, State 1, Line 1
> The proposed new database owner is already a user or aliased in the
> database.
> I can only change the Owner to sa and for any other USER if throws me the
> error I mentioned above.My question here is , Even though I upgraded the
> existing instance of 2000 to 2005, why is that only for 5 databases I am
> seeing this kind of behaviour.
> Every thing was fine when it was in sql 2000.I was able to change the DB
> Owner...
>
> Thanks
> "Uri Dimant" wrote:
>|||The users in the databases have respective logins on the server. There are n
o
orphaned users on the database. The issue is we cannot change the DB owner t
o
the existing users in the database except for SA.
"jebuskrust@.gmail.com" wrote:

> Sounds like a phantom user situation which is causing your error to be
> thrown.
> Check out http://sta.c64.org/sqlprg.html
> And download http://sta.c64.org/sqlprg/fixusers.zip
> Before you run the script be sure and read what it does.
> Good luck to ya.
>
> IT wrote:
>|||IT (IT@.discussions.microsoft.com) writes:
> The users in the databases have respective logins on the server. There
> are no orphaned users on the database. The issue is we cannot change the
> DB owner to the existing users in the database except for SA.
That is not possible on SQL 2000 either.
The login that owns the database always maps to the dbo user. If the login
already maps to a user in the database, the login can't become the database
owner, because he would then map to two users.
Thus you need to explicitly drop the users that you want to own the
databases.
I can't answer why you only got a problem with 5 of 20 databases. The
answer for that may be hidden in their previous history.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx