Cannot create diagrams in SQLSERVER 2005

Hi,
Every time I click on the Database Diagram node in object explorer in SQL
Server Management Studio, I get a message:
Database diagram support objects cannot be installed because this database
does not have a valid owner. ...
I have checked the owner and it coincides with my logon name in my domain
(i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
problem with Active Directory? Why am I not being recognized as a valid db
owner?
Thanks in advance,
Juan Dent, M.Sc.
Make sure the compatibility level of the databases is set to
90 - that's often what causes the problem.
You can set it to 90 using:
EXEC sp_dbcmptlevel 'database name', '90'
-Sue
On Mon, 23 Jan 2006 17:04:01 -0800, Juan Dent
<Juan_Dent@.nospam.nospam> wrote:

>Hi,
>Every time I click on the Database Diagram node in object explorer in SQL
>Server Management Studio, I get a message:
> Database diagram support objects cannot be installed because this database
>does not have a valid owner. ...
>I have checked the owner and it coincides with my logon name in my domain
>(i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
>problem with Active Directory? Why am I not being recognized as a valid db
>owner?
|||Juan Dent (Juan_Dent@.nospam.nospam) writes:
> Every time I click on the Database Diagram node in object explorer in SQL
> Server Management Studio, I get a message:
> Database diagram support objects cannot be installed because this
> database does not have a valid owner. ...
> I have checked the owner and it coincides with my logon name in my domain
> (i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
> problem with Active Directory? Why am I not being recognized as a valid db
> owner?
This typically happens when you migrate a database from another server.
The problem can be seen by SELECT * FROM sys.database_principals. Compare
the row for dbo with a database created on the server.
I think changing the ownership to some other login, and back to yourself
fixes the issues.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
|||This site will help. There are two quick steps.
http://mcfunley.com/cs/blogs/dan/arc...12/23/899.aspx

************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.
Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "An error has occurred while establishing a
>connection to the server. When connecting to SQL Server 2005, this failure
>may be caused by the fact that under the default settings SQL Server does
>not allow remote connections. (provider: SQL Network Interfaces, error:
>26 - Error Locating Server/Instance Specified)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by the fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "An error has occurred while establishing a
>connection to the server. When connecting to SQL Server 2005, this failure
>may be caused by the fact that under the default settings SQL Server does
>not allow remote connections. (provider: SQL Network Interfaces, error:
>26 - Error Locating Server/Instance Specified)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.