Re: Do SqlServer 2000 & SqlServer 2005 co-exist
- From: "Rick Byham, \(MSFT\)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Oct 2008 09:26:24 -0700
A TCP port can only be used by one process. Either SQL Server 2000 or SQL Server 2005. Not both. So you have to move one of them to another port.
You could allow an program exception in your firewall instead of a port number exception. However I lean towards configuring SQL Server to use a fixed port and opening that port.
So, one possible solution, is to leave SQL Server 2000 on port 1433.
Configure a fixed port for SQL Server 2005, such as port number 49172. For details see Configuring a Fixed Port at http://msdn.microsoft.com/en-us/library/ms345327.aspx
Open that port number in the firewall.
Also open UDP port 1434 so that the SQL Server Browser Service can tell your clients what port you are using.
Lots more info at http://msdn.microsoft.com/en-us/library/cc646023.aspx
These links are for SQL Server 2008, but they apply equally to SQL Server 2005. SQL Server 2000 works differently, but SP4 understands the SQL Server 2005 Browser Service so you are fine.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.
"joef" <joef@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D9B565F6-67D3-4D0B-A857-87CDA4FDF47A@xxxxxxxxxxxxxxxx
I've got the opposite problem. I have a server that had SQL server 2000 SP4
as the default instance. I then installed SQL server 2005 as a named
instance. I noticed that port 1433 was used for the 2000 instance but that
no ports were listed for the 2005 instance. Other servers can connect to the
2000 instance but cannot connect to the 2005 instance. I think this is
because our firewall is not allowing the port (whatever it is dymanically
using) to that server. We only open the ports that we need.
When I tried setting the SQL 2005 to 1433, the service wouldn't start,
saying that port is already in use. Do I need to select some other port, say
1435 and set the SQL 2005 to use that port and then open that port on our
firewall?
thanks,
Joe
--
joe
"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.aspx?scid=kb;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.aspx?scid=kb;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.
======================================================
.
- References:
- Prev by Date: Re: RAM Usage on SQL Server
- Next by Date: MSSQL and ANtivirus
- Previous by thread: Re: Do SqlServer 2000 & SqlServer 2005 co-exist
- Next by thread: Re: Migrating SQL Server
- Index(es):
Relevant Pages
|
