Re: Cannot view DB properties

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A8BF2B36-4223-49A6-948B-E5097FC52082@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx) 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 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..

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@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx




.

Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... looking at the database table information, ... Microsoft Windows SharePoint Services 2.0 ... Can we asume you mean SQL Server 2005? ... The upgrade identified that there was a previous ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: HELP - I goofed when creating a database
    ... details) go to which date record - is not stored in your database; ... some reading on the merits of SQL Server vs Access. ... you select the owner or enter a new one, enter the date ordered, then ... ownerID - PK ...
    (comp.databases.ms-access)
  • Re: Upgrade from MSDE to SQL
    ... Hard to say whether the database is of any use to you now you are partway ... upgrade just in case. ... But FIRST I would in any case see if adding SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Upgrade 2000 to 2005
    ... That way, if there is a failure in the upgrade process, you at ... Senior Database Administrator ... Real-world stuff I run across with SQL Server: ... side and move the databases but the hardware just aint there. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Upgrading from SQL 6.5 to SQL 2000
    ... transferring the objects and data from within Enterprise Manager. ... > database to a physically separate SQL server 2000. ... >> You have to upgrade the database to SQL 2000 using the upgrade wizard ...
    (microsoft.public.sqlserver.tools)