January 12, 2009 at 8:25 am
Im getting the error below on one of my clients databases when trying to access the properties.
"Property Owner is not available for Database '[database_name]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights".
There are two versions of this database. One is production and one is development (on two different servers). I can see the properties of the production database without any problem but not the development.
both databases have the exact same owner.
The database owner_ sid and the server pricipal sid do not match on either of the databases which are on different servers. I read about changing the database owner on the development. But the same case is happening on the production and I can still see the properties. So there is no point in changing database owner.
why can I see the properties of the production and not the development.
Anyone seen this or can help?
Thanks
January 12, 2009 at 8:26 am
What rights/roles does your user account have on both servers?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 12, 2009 at 8:31 am
It is a SQL login that is the database owner of both and this login has public and db_owner rights to both databases.
January 12, 2009 at 1:29 pm
What version of SQL server is this?
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 13, 2009 at 6:20 am
Both servers/databases are SQL Server 2005 service pack 2.
January 13, 2009 at 10:01 am
To see property of the database the default user "dbo" on that database should have to be associated with proper login...Go to security tab of that database and locate dbo user and see that it is associated with a login or not...if not then use sp_change_users_login procedure and associated that dbo user with a login...
January 13, 2009 at 12:49 pm
Ok, so I compared this on both databases. It's the same on both databases. The dbo login is associated with the sa user. The sa user has both public and sysadmin rights.
The login that is the owner of the database has the same privileges on both databases. I don't understand this. 🙁
January 13, 2009 at 1:57 pm
Are you able to run queries against the database???
If you are try running this
Exec sp_changedbowner 'sa'
and then try again.
Let me know if doesnt work. It worked for me previously.
January 13, 2009 at 1:59 pm
I'm not sure I want to change the database owner. Is this safe? Can it mess up anything?
January 13, 2009 at 2:00 pm
It is absolutely safe. You are not giving the ownership to anybody. Even some companies have standard that the owner should be SA.
So even anybody leaves there shouldnt be any problem.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply