Re: sql2005 "Invalid Owner.."

In my previous response I expressed concern that the user properties did not
reflect a login. What I've subsequently realized is that the user in
question was NOT the dbo. The properties of the dbo user show the correct
login information. So, I apparently have an ill formed user (under my own
name), but the dbo user looks right.

Regards,
Bill

"Charles Wang[MSFT]" <changliw@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:vwJ0xm9JHHA.2300@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Bill,
Merry Christmas!
Thanks for your post!

From your description, I understand that:
You encountered the error regarding database diagram when you attempted to
view your database diagrams. You had checked that your logon account was
the database owner.
If I have misunderstood, please let me know.

I would like to know if your database compatibility level was 90. You can
check that via the following methods:
a. Right click your database, click Properties, select Options, and see if
the Compatibility level is SQL Server 2005 (90); if not, please change it
to SQL Server 2005 (90).
b. Run the statement "sp_dbcmptlevle 'database name'". If the result is
not
90, please run the statement "sp_dbcmptlevle 'database name',90" to change
it to 90.
After changing your database compatibility to 90, you can try again.

If this issue persists, please use a sysadmin account log on your SQL
Server and run the following statement:
ALTER AUTHORIZATION ON DATABASE::database_name TO valid_login

You may also refer to the section 4.8.1 of this article:
SQL Server 2005 Readme and installation requirements
http://support.microsoft.com/default.aspx?scid=kb;EN-US;910228

If you have any other questions or concerns, please feel free to let me
know. It is my pleasure to be of assistance.

Charles Wang
Microsoft Online Partner Support

PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!

Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================



.

Relevant Pages

  • Re: System Administrator Implied Permissions
    ... > sa login, it assigns it the System Administrator fixed ... > Now, given this, why does SQL Server ... in each database is always a member of the public and db_owner roles. ... Other sysadmin role members have the exact same ...
    (microsoft.public.sqlserver.security)
  • Re: No db access after publishing web site
    ... GRANT UPDATE TO ... If I detach and attach this database on a different PC (according that PC ... Cannot open database "pago" requested by the login. ... Are you detaching/attaching the SQL Server Express database correctly ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: cannot login to the db after...
    ... Jasper Smith (SQL Server MVP) ... I have created a new database, "db_1", using the "sa" ... I then created a new login, "sqluser1" and gave ...
    (microsoft.public.sqlserver.security)
  • Re: Cant view merge agent properties (trying again)
    ... In the List of Actions for the Snapshot Agent History I see this repeated: ... every single database listed. ... So, just now, I went to computername\Administrator Login ID (because it's ... On the computer running SQL Server, ...
    (microsoft.public.sqlserver.replication)
  • Re: Database security design with ASP.net and form-based authentication
    ... Since you already have forms-based security, why not use a single SQL login ... for all database access? ... data entry, guest/view only, admin, report viewer. ... so I'm using SQL Server authentication. ...
    (microsoft.public.sqlserver.security)