Hi,
I've got an SQL server 2000 (sp3).
This box has multiple IP addresses. These are for web pages
But i only want the SQL server (port 1433) to listen on one of these addressses.
It seems to listen on all the addresses which i don't want it to. for sercuirty reasons as well
as for it's resource sake.
I've poked around in the properties and connection settings and it doesn't seem to let you change IP's only ports etc.
Please let me know how i can work this out..
Thankyou
There is no way to prevent SQL Server from listening on all the ip
addresses that are bound to NIC cards on the machine. If you want to limit
the ones that clients can connect to then that will have to be impletmented
at the client level.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Showing posts with label box. Show all posts
Showing posts with label box. Show all posts
Friday, March 30, 2012
Multiple IP's. Only want 1 for SQL 1433
Hi,
I've got an SQL server 2000 (sp3).
This box has multiple IP addresses. These are for web pages
But i only want the SQL server (port 1433) to listen on one of these address
ses.
It seems to listen on all the addresses which i don't want it to. for sercui
rty reasons as well
as for it's resource sake.
I've poked around in the properties and connection settings and it doesn't s
eem to let you change IP's only ports etc.
Please let me know how i can work this out..
ThankyouThere is no way to prevent SQL Server from listening on all the ip
addresses that are bound to NIC cards on the machine. If you want to limit
the ones that clients can connect to then that will have to be impletmented
at the client level.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I've got an SQL server 2000 (sp3).
This box has multiple IP addresses. These are for web pages
But i only want the SQL server (port 1433) to listen on one of these address
ses.
It seems to listen on all the addresses which i don't want it to. for sercui
rty reasons as well
as for it's resource sake.
I've poked around in the properties and connection settings and it doesn't s
eem to let you change IP's only ports etc.
Please let me know how i can work this out..
ThankyouThere is no way to prevent SQL Server from listening on all the ip
addresses that are bound to NIC cards on the machine. If you want to limit
the ones that clients can connect to then that will have to be impletmented
at the client level.
Rand
This posting is provided "as is" with no warranties and confers no rights.
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?
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
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?
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?
Monday, March 26, 2012
Multiple Instance Uninstall
There are 3 multiple instances running on my production
box and one of them needs unistalling.
If i use add/remove fromt he control panel to remove that
instance will it require a reboot or will there be any
issues to the other instances running?
Thanks
ApHi,
If you just want to Uninstall you do not want to reboot. But if you need to
install it again then you may need to reboot the server.
Note:
It is always recommended to unstall and reboot the server during a green
zone (Downtime)
Thanks
Hari
SQL Server MVP
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:021e01c53984$5d29e460$a601280a@.phx.gbl...
> There are 3 multiple instances running on my production
> box and one of them needs unistalling.
> If i use add/remove fromt he control panel to remove that
> instance will it require a reboot or will there be any
> issues to the other instances running?
> Thanks
> Ap
box and one of them needs unistalling.
If i use add/remove fromt he control panel to remove that
instance will it require a reboot or will there be any
issues to the other instances running?
Thanks
ApHi,
If you just want to Uninstall you do not want to reboot. But if you need to
install it again then you may need to reboot the server.
Note:
It is always recommended to unstall and reboot the server during a green
zone (Downtime)
Thanks
Hari
SQL Server MVP
"Ap" <anonymous@.discussions.microsoft.com> wrote in message
news:021e01c53984$5d29e460$a601280a@.phx.gbl...
> There are 3 multiple instances running on my production
> box and one of them needs unistalling.
> If i use add/remove fromt he control panel to remove that
> instance will it require a reboot or will there be any
> issues to the other instances running?
> Thanks
> Ap
Friday, March 23, 2012
Multiple group default database
SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
local groups on the SQL Server box, and each local group maps to a SQL Serve
r
login, and the logins have different default databases, how do you determine
what default database is used for a given Windows login?
Thanks
VernVern,
There is an order. When I tested it seemed like alphabetical order, but I
did not absolutely verify it. Try assigning the first alphabetical group
for a user to default to a database where he has no rights and see if this
causes a login failure.
RLF
"Vern Rabe" <VernRabe@.discussions.microsoft.com> wrote in message
news:7C825239-6888-4DEC-BE0B-59CFB3D2764A@.microsoft.com...
> SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
> local groups on the SQL Server box, and each local group maps to a SQL
> Server
> login, and the logins have different default databases, how do you
> determine
> what default database is used for a given Windows login?
> Thanks
> Vernsql
local groups on the SQL Server box, and each local group maps to a SQL Serve
r
login, and the logins have different default databases, how do you determine
what default database is used for a given Windows login?
Thanks
VernVern,
There is an order. When I tested it seemed like alphabetical order, but I
did not absolutely verify it. Try assigning the first alphabetical group
for a user to default to a database where he has no rights and see if this
causes a login failure.
RLF
"Vern Rabe" <VernRabe@.discussions.microsoft.com> wrote in message
news:7C825239-6888-4DEC-BE0B-59CFB3D2764A@.microsoft.com...
> SQL Server 2000. Windows Auth. If a Windows login is a member of multiple
> local groups on the SQL Server box, and each local group maps to a SQL
> Server
> login, and the logins have different default databases, how do you
> determine
> what default database is used for a given Windows login?
> Thanks
> Vernsql
Monday, March 19, 2012
multiple datasets
Is it possible to have more than one dataset in a report?
I'm trying to create a parameter that draws its drop down box values from a query that is seperate from the result set.
Thanks
Yes, you can have multiple DataSets in reports. You can set up a DatsSet to be the source for valid parameter values like you describe.
-Chris
Subscribe to:
Posts (Atom)