Can I put both on the same server without any conflicts or other problems? Or
do they fight for the TCP port to respond to client requests?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

You can install them both without conflict. There will not be any port
conflicts.

One will be the default Server, known as {computername}, and the other will
have an Instance Name, and be addressed as {computername\InstanceName}. Any
application seeking a SQL Server by the IP will be directed to the default
server.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


"David Thielen" <thielen@nospam.nospam> wrote in message
news:7C6CF9B6-CB9A-4E15-B8E5-9531057768FB@microsoft.com...
> Can I put both on the same server without any conflicts or other problems?
> Or
> do they fight for the TCP port to respond to client requests?
>
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
>
> Cubicle Wars - http://www.windwardreports.com/film.htm
>
>

Hello David,

I agree with Arnie that you shall not encounter conflicts or port confusion
from clients. You could install SQL 2005 or 2000 as a default instance and
the other version as a named instance. For default instance, the default
port is 1433. For named instance, it is dynamical but you could configure
it as fixed port.

Certainly you could install both SQL 2005 and 2000 as named instance. Also,
the ports of both instances are dynamical got and you could configure it as
fixed ones.

You could run SQL Server configuration manager to configure TCPIP protocals
of SQL 2005 instances. As for SQL 2000 instances, ususally you shall use
SQL 2000 server network utility.

Usually clients shall query server to get the dynamical port of named
instance, and then connect to that instance.

INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932

If you do encounter issues when connecting to named instance of SQL Server,
you may want to configured a fixed port on server/cleint to test.

Please feel free to let's know if you have any further questions or
concerns. I look forward to your reply. Thank you!

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi;

Ok I installed SqlServer 2000 on a machine that already had SqlServer 2005.
When I installed I had to enter an instance name for it and entered the name
SqlServer2K.

I can bring it up on the server using EnterpriseManager fine. But I cannot
connect with EnterpriseManager from my workstation. I can still convert to
Sql Server 2005, but not Sql Server 2000.

I have tried both Windows Authentication and the sa login from my
workstation. I get cannot establish connection or cannot login.

Also, when I run the wizard to connect, it does not show the server as a
choice - I have to type it in.

Any ideas?

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm




"Arnie Rowland" wrote:

> You can install them both without conflict. There will not be any port
> conflicts.
>
> One will be the default Server, known as {computername}, and the other will
> have an Instance Name, and be addressed as {computername\InstanceName}. Any
> application seeking a SQL Server by the IP will be directed to the default
> server.
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
>
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> You can't someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
>
> "David Thielen" <thielen@nospam.nospam> wrote in message
> news:7C6CF9B6-CB9A-4E15-B8E5-9531057768FB@microsoft.com...
> > Can I put both on the same server without any conflicts or other problems?
> > Or
> > do they fight for the TCP port to respond to client requests?
> >
> > --
> > thanks - dave
> > david_at_windward_dot_net
> > http://www.windwardreports.com
> >
> > Cubicle Wars - http://www.windwardreports.com/film.htm
> >
> >
>
>
>

Hello Cubicle,

I understand that you can connect to SQL 2000 named instance on the local
console of server. However, you cannot cannot it from client machines.

Since you installed SQL 2000 after 2005 instance, you may encounter the
known issue documented in the following article


905618 You may receive a connection error message when you try to connect
to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed
after you installed SQL Server 2005
http://support.microsoft.com/default...b;EN-US;905618


You may want to test if above article fix the problem. When you have a
named instance of SQL Server 2000 that is running side-by-side with an
instance of SQL Server 2005 on the same computer, the SQL Server 2005
Browser service listens on UDP port 1434 for incoming requests for the
named instance of SQL Server 2000.

If the issue still occurs, it seems the instance was blocked by the
firewall. Going forward, I suggest that you try the following steps to
isolate the issue:

1. Click Start->ALL Programs->Microsoft SQL Server, run SQL 2000 Sever
network utility, select SQL 2000 server name (servername\instancename).

2. Make sure TCPIP and Named Pipes protocol are enabled

3. Select TCPIP, and click Properties, and set the port of the instance to
a fixed port such as 1500.

4. Restart SQL 2000 named instance.

5. Run "Client Network utility" on the server, on Alias type, add a alias
such as test, select TCPIP, type the server computer name in Server name.

6. Check if you could connect to Alias on the local server.

7. If you have firewall enabled on your computer, please open the port.
Please note, in Win2003 sp1, you could configure Windows firewall in the
Control Panel. Please refer to the following article as I mentioned for
details.

INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932

8. Run "Client Network utility" on the client machine, and create Alias as
described in setp 5. If you encounter any problem from this step, you may
want to use "telnet <servername> 1500 to see if you could connect to the
port you configure from client machine.

If you encounter any error message, please let's know exact message.

More related information

922131 You cannot remotely connect to a named instance of SQL Server 2000
by using the TCP/IP protocol
http://support.microsoft.com/default...b;EN-US;922131

I look forward to your reply. Thanks.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===


This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

The KB article gave me the needed fix

--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm




"Peter Yang [MSFT]" wrote:

> Hello Cubicle,
>
> I understand that you can connect to SQL 2000 named instance on the local
> console of server. However, you cannot cannot it from client machines.
>
> Since you installed SQL 2000 after 2005 instance, you may encounter the
> known issue documented in the following article
>
>
> 905618 You may receive a connection error message when you try to connect
> to an instance of SQL Server 2000 or of SQL Server 7.0 that was installed
> after you installed SQL Server 2005
> http://support.microsoft.com/default...b;EN-US;905618
>
>
> You may want to test if above article fix the problem. When you have a
> named instance of SQL Server 2000 that is running side-by-side with an
> instance of SQL Server 2005 on the same computer, the SQL Server 2005
> Browser service listens on UDP port 1434 for incoming requests for the
> named instance of SQL Server 2000.
>
> If the issue still occurs, it seems the instance was blocked by the
> firewall. Going forward, I suggest that you try the following steps to
> isolate the issue:
>
> 1. Click Start->ALL Programs->Microsoft SQL Server, run SQL 2000 Sever
> network utility, select SQL 2000 server name (servername\instancename).
>
> 2. Make sure TCPIP and Named Pipes protocol are enabled
>
> 3. Select TCPIP, and click Properties, and set the port of the instance to
> a fixed port such as 1500.
>
> 4. Restart SQL 2000 named instance.
>
> 5. Run "Client Network utility" on the server, on Alias type, add a alias
> such as test, select TCPIP, type the server computer name in Server name.
>
> 6. Check if you could connect to Alias on the local server.
>
> 7. If you have firewall enabled on your computer, please open the port.
> Please note, in Win2003 sp1, you could configure Windows firewall in the
> Control Panel. Please refer to the following article as I mentioned for
> details.
>
> INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
> http://support.microsoft.com/kb/287932
>
> 8. Run "Client Network utility" on the client machine, and create Alias as
> described in setp 5. If you encounter any problem from this step, you may
> want to use "telnet <servername> 1500 to see if you could connect to the
> port you configure from client machine.
>
> If you encounter any error message, please let's know exact message.
>
> More related information
>
> 922131 You cannot remotely connect to a named instance of SQL Server 2000
> by using the TCP/IP protocol
> http://support.microsoft.com/default...b;EN-US;922131
>
> I look forward to your reply. Thanks.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
>
> ================================================== ===
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>