Thursday, March 8, 2012

Database diagram in SQL Server 2005

I cannot create a database diagram in SQL Server 2005.
When I try to create a diagram I receive the message that the database does
not have a valid owner. I changed the database owner to sa and yet the
message persists.
I get this invalid owner messsage when I try to create a new database
diagram or install support for diagrams.
Has anyone else experienced this problem?Dave
Did you upgrade the database to SQL Server 2005 or it was initialy created
?
"Dave" <davefrick@.newsgroup.nospam> wrote in message
news:uChrIOS9GHA.1012@.TK2MSFTNGP05.phx.gbl...
>I cannot create a database diagram in SQL Server 2005.
> When I try to create a diagram I receive the message that the database
> does not have a valid owner. I changed the database owner to sa and yet
> the message persists.
> I get this invalid owner messsage when I try to create a new database
> diagram or install support for diagrams.
> Has anyone else experienced this problem?
>|||What is the compatibility mode of the database?
You can check with:
select compatibility_level
from sys.databases
where name = 'YourDatabase'
It needs to be at 90 to use the diagrams. You can change it
to 90 with:
EXEC sp_dbcmptlevel YourDatabase, 90
I think this was fixed in the service pack so the other
alternative is to apply SP1.
-Sue
On Sat, 21 Oct 2006 09:03:22 -0700, "Dave"
<davefrick@.newsgroup.nospam> wrote:
>I cannot create a database diagram in SQL Server 2005.
>When I try to create a diagram I receive the message that the database does
>not have a valid owner. I changed the database owner to sa and yet the
>message persists.
>I get this invalid owner messsage when I try to create a new database
>diagram or install support for diagrams.
>Has anyone else experienced this problem?
>|||Hi,
My understanding of your issue is that:
You cannot create a database diagram on your database due to the invalid
owner error:
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.
If I have misunderstood, please let me know.
This issue is caused by the database compatibility. If the database is not
in 90 compatibility level, the error will occcur.
Please run the following statements to resolve this issue:
USE master
GO
EXEC sp_dbcmptlevel 'your_database_name', '90';
ALTER AUTHORIZATION ON DATABASE::your_database_name TO [your_login_name]
GO
For more information, please refer to:
Understanding Database Diagram Ownership (Visual Database Tools)
http://msdn2.microsoft.com/en-us/library/ms186345.aspx
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Community Support
======================================================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.
======================================================|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support|||I have this same issue at the moment, and I am on compatibility level 90. I
have other databases on the same server for which I am able to use database
diagramming.
"Charles Wang[MSFT]" wrote:
> Hi,
> I am interested in this issue. Would you mind letting me know the result of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||I have the same issue. My database is set with compatibility level 90. I
have other databases in the same instance of SQL server for which I can use
database diagrams.
"Charles Wang[MSFT]" wrote:
> Hi,
> I am interested in this issue. Would you mind letting me know the result of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||what i did to fix this was go to database your working with, go to
properties, click on FILES and then add the SA account to the owner... done!
"lund0529" wrote:
> I have the same issue. My database is set with compatibility level 90. I
> have other databases in the same instance of SQL server for which I can use
> database diagrams.
> "Charles Wang[MSFT]" wrote:
> > Hi,
> >
> > I am interested in this issue. Would you mind letting me know the result of
> > the suggestions? If you need further assistance, feel free to let me know.
> > I will be more than happy to be of assistance.
> >
> > Have a great day!
> >
> > Charles Wang
> > Microsoft Online Community Support
> >
> >|||Thanks Charles.
Setting the compatibility level to 90 solved my problem.
Dave
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:PJRiU9N%23GHA.4432@.TK2MSFTNGXA01.phx.gbl...
> Hi,
> I am interested in this issue. Would you mind letting me know the result
> of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Dave,
Appreciate your update and response. I am glad to hear that the problem has
been fixed. If you have any other questions or concerns, please do not
hesitate to contact us. It is always our pleasure to be of assistance.
Have a nice day!
Charles Wang
Microsoft Online Community Support
======================================================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.
======================================================

No comments:

Post a Comment