Error creating Database Diagrams

I'm using MS SQL Server Management Studio 2005 to manage both SQL 2000 and SQL 2005 server. When I connect to SQL 2000 Server database and try to do a Database Diagram, I got the following error:

SQL Server 2005 database diagrams and SQL Server 2000 database diagrams are created and rendered differently. Because of these differences, SQL Server Management Studio cannot work with SQL Server 2000 diagrams. Use SQL Server 2000 Enterprise Manager.

When a database containing diagrams is upgraded to SQL Server 2005, the diagrams will be upgraded the first time that the diagrams folder is opened.

You must be a member of the db_owner database role to upgrade database diagrams.

Any idea how to resolve this? I do not have admin rights to the SQL Server 2000.

Use SQL Server 2000 to administer the on the SQL Server 2000 Server stored diagrams.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.
Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error Capture in Procedure?

Is there anyway to capture and manage errors in a procedure so it can
proceed?
(The server keeps deleting my posts; I hope this one gets through)
TIA!
--
Greg CHi Greg.
There are error handling mechanisms in SQL Server, but they do not allow you
to catch or handle or errors.
Ultimately, you cannot handle all t-sql errors in stored procedures.
There is a good article on the topic here:
http://www.sommarskog.se/
HTH
Regards,
Greg Linwood
SQL Server MVP
"Greg C" <gregc@.austinps.com> wrote in message
news:fT%Mb.16281$RV5.7088@.fe2.texas.rr.com...
> Is there anyway to capture and manage errors in a procedure so it can
> proceed?
> (The server keeps deleting my posts; I hope this one gets through)
> TIA!
> --
> Greg C
>|||Thanks Greg.
--
Greg C
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:#BR3XZk2DHA.2888@.tk2msftngp13.phx.gbl...
> Hi Greg.
> There are error handling mechanisms in SQL Server, but they do not allow
you
> to catch or handle or errors.
> Ultimately, you cannot handle all t-sql errors in stored procedures.
> There is a good article on the topic here:
> http://www.sommarskog.se/
> HTH
> Regards,
> Greg Linwood
> SQL Server MVP
> "Greg C" <gregc@.austinps.com> wrote in message
> news:fT%Mb.16281$RV5.7088@.fe2.texas.rr.com...
> >
> > Is there anyway to capture and manage errors in a procedure so it can
> > proceed?
> >
> > (The server keeps deleting my posts; I hope this one gets through)
> >
> > TIA!
> >
> > --
> >
> > Greg C
> >
> >
>

Error Capture in Procedure?

Is there anyway to capture and manage errors in a procedure so it can
proceed?
(The server keeps deleting my posts; I hope this one gets through)
TIA!
Greg CHi Greg.
There are error handling mechanisms in SQL Server, but they do not allow you
to catch or handle or errors.
Ultimately, you cannot handle all t-sql errors in stored procedures.
There is a good article on the topic here:
http://www.sommarskog.se/
HTH
Regards,
Greg Linwood
SQL Server MVP
"Greg C" <gregc@.austinps.com> wrote in message
news:fT%Mb.16281$RV5.7088@.fe2.texas.rr.com...

quote:

---

> Is there anyway to capture and manage errors in a procedure so it can
> proceed?
> (The server keeps deleting my posts; I hope this one gets through)
> TIA!
> --
> Greg C
>

---

|||Thanks Greg.
Greg C
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:#BR3XZk2DHA.2888@.tk2msftngp13.phx.gbl...

quote:

---

> Hi Greg.
> There are error handling mechanisms in SQL Server, but they do not allow

---

you

quote:

---

> to catch or handle or errors.
> Ultimately, you cannot handle all t-sql errors in stored procedures.
> There is a good article on the topic here:
> http://www.sommarskog.se/
> HTH
> Regards,
> Greg Linwood
> SQL Server MVP
> "Greg C" <gregc@.austinps.com> wrote in message
> news:fT%Mb.16281$RV5.7088@.fe2.texas.rr.com...
>

---