Saturday, February 25, 2012

Managing 2000 and 2005

Dear all
I have now a default instance of SQL Server 2005 running on one PC and an
old default instance of SQL Server 2000 running on another PC.
I would like to administer both SQL Servers with the new SQL Server 2005
Management Studio. However, I am unable to register the SQL Server 2000 in
the SQL Server 2005 Management Studio.
Any help is appreciated.
Best regards
AdrianYou should be able to.
What problems are you seeing?
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
"Unable to register" means what exactly? Are you getting an error
message? Management Studio is perfectly capable of working with a 2000
server, I do it all day long every day...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525017F.8020007@.realsqlguy.com...
> Adrian wrote:
> "Unable to register" means what exactly? Are you getting an error
> message? Management Studio is perfectly capable of working with a 2000
> server, I do it all day long every day...
Well, it is great to hear it. So I just need to figure out how.
I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
blink. However, when I enter precisely the same connect data to the
register-dialog of the Management Studio it returns after quite a long time
a message with the error 10061.
So what am I doing wrong?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||You should be able to connect to a SQL Server 2000 box from the SQL Server
2005 tools (including SSMS, Profiler, and the Replication Monitor
(sqlmonitor).
Keith Kratochvil
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Well, it is great to hear it. So I just need to figure out how.
> I can connect to the SQL Server 2000 with the sqlcmd program within an eye
's
> blink. However, when I enter precisely the same connect data to the
> register-dialog of the Management Studio it returns after quite a long tim
e
> a message with the error 10061.
> So what am I doing wrong?
That error indicates that the connection was refused by the server. Is
SQL Server using TCP/IP? Listening on what port?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45250DE5.8030609@.realsqlguy.com...
> Adrian wrote:
> That error indicates that the connection was refused by the server. Is
> SQL Server using TCP/IP? Listening on what port?
Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
connecting to it. It is only the Management Studio that makes me ...
aaarrrgh.
Any ideas?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Adrian wrote:
> Yes, it listens on TCP/IP 2433 and requires encryption. The client librari
es
> on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problem
s
> connecting to it. It is only the Management Studio that makes me ...
> aaarrrgh.
> Any ideas?
>
In the connection dialog in Management Studio, try specifying the server
name like this:
serverDNSname,2433
And in the Options of that connection dialog, make sure the "Encrypt
Connection" checkbox is marked...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Firewalls?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Deal all
Thank you very much for the excellent and very quick help.
Yes, the connection is established.
The trick is:
i) to follow this advice:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
but
ii) not to follow this one:
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
Now my sleep will be peaceful.
Best regards
Adrian
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

No comments:

Post a Comment