Multiple instances with different TCP ports

I was wondering whether I can configure SQL instances with different TCP
ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able to
assign only one port to TCP at the client machines using "Client Network
Utility". Is there a way to set different TCP port to each instance?
Have you tried using an alias? See How to configure a client to use TCP/IP
(Client Network Utility) in SQL BOL.
HTH
Jerry
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?
|||Actually, I tried usng Alias. If I use port 1433, it works for both
instances. However, if I change the port to 1432 for SQL2K5 instance (in
alias), it fails. I have a feeling that the tcp port setting at the server
may not be working. I am setting Microsoft SQL Server 2006 --> SQL Computer
Manager --> Protocols fpr SQLB --> TCP --> IP1 to port 1432.
"Jerry Spivey" wrote:

> Have you tried using an alias? See How to configure a client to use TCP/IP
> (Client Network Utility) in SQL BOL.
> HTH
> Jerry
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>
|||I dont know about SQL2K5
But in SQL 2000 by using server network utility, under enabled protocols,
click on TCP/IP then click Properties button and you can change port SQL2K
listens on. Then use and alias in Client Net Util to go to dif port.
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?
|||I have no problem with SQL2K. Thanks.
"David J. Cartwright" wrote:

> I dont know about SQL2K5
> But in SQL 2000 by using server network utility, under enabled protocols,
> click on TCP/IP then click Properties button and you can change port SQL2K
> listens on. Then use and alias in Client Net Util to go to dif port.
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>
|||Hi,
Use Server Network utlity to change ports. After changing restart sql server
service.
Thanks
Hari
SQL Server MVP
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?
|||Hi Hari,
Server Network Utility is in SQL 2000. However, it is
'SQLComputer Manager' in SQL server 2005.
To recape the issue, I have one SQL 2000 instance (SQLA) and one
SQL 2005 instance (SQLB). I am trying to assign different ports. Both are
working if I assign the same port. If I assign different ports, SQLB is
failing to respond to client (running enterprise manager or management
studio). Is there a conflict in registry?
"Hari Prasad" wrote:

> Hi,
> Use Server Network utlity to change ports. After changing restart sql server
> service.
> Thanks
> Hari
> SQL Server MVP
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>
|||Hi Hari,
I could find a way to do this at client. I installed "workstation"
components (of SQ 2005) at the client. Then, I defined alias for SQLserrver
2005 instance with port (ez., <server name>\SQLB,1432) using SQL computer
manager of 2005. Then, I used SQL Server Management Studio to conect to both
instances (SQLA (2000) and SQLB (2005) ) on the server. It seems that SQL
server 2000 Enterprise Manager does not work for SQL server 2005.
Please let me know if there is a clean procedure.
"doc pisapati" wrote:

> I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?

Multiple instances with different TCP ports

I was wondering whether I can configure SQL instances with different TCP
ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able t
o
assign only one port to TCP at the client machines using "Client Network
Utility". Is there a way to set different TCP port to each instance?Have you tried using an alias? See How to configure a client to use TCP/IP
(Client Network Utility) in SQL BOL.
HTH
Jerry
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||Actually, I tried usng Alias. If I use port 1433, it works for both
instances. However, if I change the port to 1432 for SQL2K5 instance (in
alias), it fails. I have a feeling that the tcp port setting at the server
may not be working. I am setting Microsoft SQL Server 2006 --> SQL Computer
Manager --> Protocols fpr SQLB --> TCP --> IP1 to port 1432.
"Jerry Spivey" wrote:

> Have you tried using an alias? See How to configure a client to use TCP/I
P
> (Client Network Utility) in SQL BOL.
> HTH
> Jerry
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>|||I dont know about SQL2K5
But in SQL 2000 by using server network utility, under enabled protocols,
click on TCP/IP then click Properties button and you can change port SQL2K
listens on. Then use and alias in Client Net Util to go to dif port.
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||I have no problem with SQL2K. Thanks.
"David J. Cartwright" wrote:

> I dont know about SQL2K5
> But in SQL 2000 by using server network utility, under enabled protocols,
> click on TCP/IP then click Properties button and you can change port SQL2K
> listens on. Then use and alias in Client Net Util to go to dif port.
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>|||Hi,
Use Server Network utlity to change ports. After changing restart sql server
service.
Thanks
Hari
SQL Server MVP
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||Hi Hari,
Server Network Utility is in SQL 2000. However, it is
'SQLComputer Manager' in SQL server 2005.
To recape the issue, I have one SQL 2000 instance (SQLA) and one
SQL 2005 instance (SQLB). I am trying to assign different ports. Both are
working if I assign the same port. If I assign different ports, SQLB is
failing to respond to client (running enterprise manager or management
studio). Is there a conflict in registry?
"Hari Prasad" wrote:

> Hi,
> Use Server Network utlity to change ports. After changing restart sql serv
er
> service.
> Thanks
> Hari
> SQL Server MVP
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>
>|||Hi Hari,
I could find a way to do this at client. I installed "workstation"
components (of SQ 2005) at the client. Then, I defined alias for SQLserrver
2005 instance with port (ez., <server name>\SQLB,1432) using SQL computer
manager of 2005. Then, I used SQL Server Management Studio to conect to both
instances (SQLA (2000) and SQLB (2005) ) on the server. It seems that SQL
server 2000 Enterprise Manager does not work for SQL server 2005.
Please let me know if there is a clean procedure.
"doc pisapati" wrote:

> I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?sql

Multiple instances with different TCP ports

I was wondering whether I can configure SQL instances with different TCP
ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able to
assign only one port to TCP at the client machines using "Client Network
Utility". Is there a way to set different TCP port to each instance?Have you tried using an alias? See How to configure a client to use TCP/IP
(Client Network Utility) in SQL BOL.
HTH
Jerry
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||Actually, I tried usng Alias. If I use port 1433, it works for both
instances. However, if I change the port to 1432 for SQL2K5 instance (in
alias), it fails. I have a feeling that the tcp port setting at the server
may not be working. I am setting Microsoft SQL Server 2006 --> SQL Computer
Manager --> Protocols fpr SQLB --> TCP --> IP1 to port 1432.
"Jerry Spivey" wrote:
> Have you tried using an alias? See How to configure a client to use TCP/IP
> (Client Network Utility) in SQL BOL.
> HTH
> Jerry
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
> >I was wondering whether I can configure SQL instances with different TCP
> > ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> > to
> > assign only one port to TCP at the client machines using "Client Network
> > Utility". Is there a way to set different TCP port to each instance?
>
>|||I dont know about SQL2K5
But in SQL 2000 by using server network utility, under enabled protocols,
click on TCP/IP then click Properties button and you can change port SQL2K
listens on. Then use and alias in Client Net Util to go to dif port.
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||I have no problem with SQL2K. Thanks.
"David J. Cartwright" wrote:
> I dont know about SQL2K5
> But in SQL 2000 by using server network utility, under enabled protocols,
> click on TCP/IP then click Properties button and you can change port SQL2K
> listens on. Then use and alias in Client Net Util to go to dif port.
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
> >I was wondering whether I can configure SQL instances with different TCP
> > ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> > to
> > assign only one port to TCP at the client machines using "Client Network
> > Utility". Is there a way to set different TCP port to each instance?
>
>|||Hi,
Use Server Network utlity to change ports. After changing restart sql server
service.
Thanks
Hari
SQL Server MVP
"doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
>I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?|||Hi Hari,
Server Network Utility is in SQL 2000. However, it is
'SQLComputer Manager' in SQL server 2005.
To recape the issue, I have one SQL 2000 instance (SQLA) and one
SQL 2005 instance (SQLB). I am trying to assign different ports. Both are
working if I assign the same port. If I assign different ports, SQLB is
failing to respond to client (running enterprise manager or management
studio). Is there a conflict in registry?
"Hari Prasad" wrote:
> Hi,
> Use Server Network utlity to change ports. After changing restart sql server
> service.
> Thanks
> Hari
> SQL Server MVP
> "doc pisapati" <docpisapati@.discussions.microsoft.com> wrote in message
> news:F1A78A23-3398-4CA5-8F98-00CF66B0F023@.microsoft.com...
> >I was wondering whether I can configure SQL instances with different TCP
> > ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able
> > to
> > assign only one port to TCP at the client machines using "Client Network
> > Utility". Is there a way to set different TCP port to each instance?
>
>|||Hi Hari,
I could find a way to do this at client. I installed "workstation"
components (of SQ 2005) at the client. Then, I defined alias for SQLserrver
2005 instance with port (ez., <server name>\SQLB,1432) using SQL computer
manager of 2005. Then, I used SQL Server Management Studio to conect to both
instances (SQLA (2000) and SQLB (2005) ) on the server. It seems that SQL
server 2000 Enterprise Manager does not work for SQL server 2005.
Please let me know if there is a clean procedure.
"doc pisapati" wrote:
> I was wondering whether I can configure SQL instances with different TCP
> ports. I did install SQL 2000 and SQL 2005 on one box. However, I was able to
> assign only one port to TCP at the client machines using "Client Network
> Utility". Is there a way to set different TCP port to each instance?

multiple instances

Hello,
I have a basic question about running multiple instances.
I would like to install 2 instances of SQL server 2000 sp3 and configure
both to the default port 1433.
I only need one up and running at any one time. So shut down one start up
the other.
Can this work? Or the way the "listener service" is configured during
install it will error on installing the second sql instance? or some other
problem?
Any help would be appreciated.As long as both aren't running at the same time then they can be configured
to listen on the same port. This can be done most easily with the server
network utility post installation. If you try and have both running, the
second one to start will have errors like "SuperSocket Info: Bind failed on
TCP port 1433." Why do you want to do this ?
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"greg" <greg@.nospam.com> wrote in message
news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hello,
> I have a basic question about running multiple instances.
> I would like to install 2 instances of SQL server 2000 sp3 and configure
> both to the default port 1433.
> I only need one up and running at any one time. So shut down one start up
> the other.
> Can this work? Or the way the "listener service" is configured during
> install it will error on installing the second sql instance? or some
> other
> problem?
>
> Any help would be appreciated.
>
>
>|||Thanks for the info.
It is a testing box. And 1 product requires case sensitivity on and one
requires it off.
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
> As long as both aren't running at the same time then they can be
configured
> to listen on the same port. This can be done most easily with the server
> network utility post installation. If you try and have both running, the
> second one to start will have errors like "SuperSocket Info: Bind failed
on
> TCP port 1433." Why do you want to do this ?
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "greg" <greg@.nospam.com> wrote in message
> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> > Hello,
> >
> > I have a basic question about running multiple instances.
> >
> > I would like to install 2 instances of SQL server 2000 sp3 and configure
> > both to the default port 1433.
> >
> > I only need one up and running at any one time. So shut down one start
up
> > the other.
> >
> > Can this work? Or the way the "listener service" is configured during
> > install it will error on installing the second sql instance? or some
> > other
> > problem?
> >
> >
> >
> > Any help would be appreciated.
> >
> >
> >
> >
> >
> >
>|||greg wrote:
> Thanks for the info.
> It is a testing box. And 1 product requires case sensitivity on and
> one requires it off.
>
>
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:OoOVIYRkEHA.2908@.TK2MSFTNGP10.phx.gbl...
>> As long as both aren't running at the same time then they can be
>> configured to listen on the same port. This can be done most easily
>> with the server network utility post installation. If you try and
>> have both running, the second one to start will have errors like
>> "SuperSocket Info: Bind failed on TCP port 1433." Why do you want to
>> do this ?
>> --
>> HTH
>> Jasper Smith (SQL Server MVP)
>> http://www.sqldbatips.com
>> I support PASS - the definitive, global
>> community for SQL Server professionals -
>> http://www.sqlpass.org
>> "greg" <greg@.nospam.com> wrote in message
>> news:%23U1gYoQkEHA.1348@.TK2MSFTNGP15.phx.gbl...
>> Hello,
>> I have a basic question about running multiple instances.
>> I would like to install 2 instances of SQL server 2000 sp3 and
>> configure both to the default port 1433.
>> I only need one up and running at any one time. So shut down one
>> start up the other.
>> Can this work? Or the way the "listener service" is configured
>> during install it will error on installing the second sql instance?
>> or some other
>> problem?
>>
>> Any help would be appreciated.
Why can't you run both instances at the same time?
--
David G.