Drop Table
Support Forum for database administrators and web based access to important newsgroups related to databases
Multiple ListenersWe have four NIC cards on Windows 2003 server running one default SQL server instance and we want the SQL server to listen all the four cards? How can one setup multiple listener for TCP-IP connection over same port 143 3. 1. NIC- 132.10.1.11 2. NIC-132.10.1.12 3. NIC-132.10.1.13 4. NIC-132.10.1.14 The clients will connect using either of the 4 networks.
Post Follow-up to this message
Re: Multiple ListenersSQL Server will listen on all addresses by default. If you are running SQL 2005, remote connections need to be enabled and you can select specific addresses. -- Hope this helps. Dan Guzman SQL Server MVP "Jen" <Jen@discussions.microsoft.com> wrote in message news:A91AB732-1CB8-4D3C-92E2- F8371A2BC6A8@microso ft.com... > We have four NIC cards on Windows 2003 server running one default SQL > server > instance and we want the SQL server to listen all the four cards? > > How can one setup multiple listener for TCP-IP connection over same port > 1433. > 1. NIC- 132.10.1.11 > 2. NIC-132.10.1.12 > 3. NIC-132.10.1.13 > 4. NIC-132.10.1.14 > > The clients will connect using either of the 4 networks. > >
Post Follow-up to this message Re: Multiple ListenersThanks Dan. Is there any way I can configure clients to automatically switch to a different if one is down? e.g. Client connecting via NIC- 132.10.1.11 should be able to connect using NIC- 132.10.1.12 if the 132.10.1.11 is down. How ca n i setup the client to use this feature? "Dan Guzman" wrote: > SQL Server will listen on all addresses by default. If you are running SQ L > 2005, remote connections need to be enabled and you can select specific > addresses. > > -- > Hope this helps. > > Dan Guzman > SQL Server MVP > > "Jen" <Jen@discussions.microsoft.com> wrote in message > news:A91AB732-1CB8-4D3C-92E2- F8371A2BC6A8@microso ft.com... > > >
Post Follow-up to this message Re: Multiple ListenersI don't think there is anything built into the SQL Server client that will automatically switch to an alternate address if a server NIC goes down. I'm not a network guy but it seems to me that this would need to be addressed at the network/OS level since it transcends SQL Server. Unless someone else chimes in, you might try posting this question to a Windows Server networking forum. -- Hope this helps. Dan Guzman SQL Server MVP "Jen" <Jen@discussions.microsoft.com> wrote in message news:76845927-D112-49E8-BA38- AC6DC80AF6E5@microso ft.com... > Thanks Dan. > > Is there any way I can configure clients to automatically switch to a > different if one is down? e.g. Client connecting via NIC- 132.10.1.11 > should > be able to connect using NIC- 132.10.1.12 if the 132.10.1.11 is down. How > can > i setup the client to use this feature? > > "Dan Guzman" wrote: >
Post Follow-up to this message Re: Multiple ListenersThanks Dan, you have been a great help. We are also running sybase, the multiple NIC client setup on sybase is simple - just add multiple query entries with multiple IP address in the sql.ini file. Though it does not switch the connections automatically but if the user tries to reconnect he gets routed through the new NIC interface. I was hoping there is something similar to this in MS SQL server. I will try m y luck in other forum. Thanks again. "Dan Guzman" wrote: > I don't think there is anything built into the SQL Server client that will > automatically switch to an alternate address if a server NIC goes down. I 'm > not a network guy but it seems to me that this would need to be addressed at > the network/OS level since it transcends SQL Server. > > Unless someone else chimes in, you might try posting this question to a > Windows Server networking forum. > > -- > Hope this helps. > > Dan Guzman > SQL Server MVP > > "Jen" <Jen@discussions.microsoft.com> wrote in message > news:76845927-D112-49E8-BA38- AC6DC80AF6E5@microso ft.com... > > >
Post Follow-up to this message Re: Multiple ListenersYou may want to consider setting up DNS entries for each of the NIC's - or you could team the NIC's. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Toronto, ON Canada . "Jen" <Jen@discussions.microsoft.com> wrote in message news:53A1EF0B-FAFA-4A6F-AB48- 54AC9484998E@microso ft.com... Thanks Dan, you have been a great help. We are also running sybase, the multiple NIC client setup on sybase is simple - just add multiple query entries with multiple IP address in the sql.ini file. Though it does not switch the connections automatically but if the user tries to reconnect he gets routed through the new NIC interface. I was hoping there is something similar to this in MS SQL server. I will try my luck in other forum. Thanks again. "Dan Guzman" wrote: > I don't think there is anything built into the SQL Server client that will > automatically switch to an alternate address if a server NIC goes down. > I'm > not a network guy but it seems to me that this would need to be addressed > at > the network/OS level since it transcends SQL Server. > > Unless someone else chimes in, you might try posting this question to a > Windows Server networking forum. > > -- > Hope this helps. > > Dan Guzman > SQL Server MVP > > "Jen" <Jen@discussions.microsoft.com> wrote in message > news:76845927-D112-49E8-BA38- AC6DC80AF6E5@microso ft.com... > > >
Post Follow-up to this message Re: Multiple ListenersThanks Tom, I am kinda new to databases. Your suggestion sounds interesting. Could you help me about how to setup "team the NIC's" stuff or point me to a place where I can grab more information? I did think of having multiple DNS entries but the third party application which we use, will need to be reconfigured everytime the primary NIC goes down. I am just hoping the user to restart the application and they get routed through a new NIC interface. Thank you both Tom and Dan. "Tom Moreau" wrote: > You may want to consider setting up DNS entries for each of the NIC's - or > you could team the NIC's. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > SQL Server MVP > Toronto, ON Canada > .. > "Jen" <Jen@discussions.microsoft.com> wrote in message > news:53A1EF0B-FAFA-4A6F-AB48- 54AC9484998E@microso ft.com... > Thanks Dan, you have been a great help. > > We are also running sybase, the multiple NIC client setup on sybase is > simple - just add multiple query entries with multiple IP address in the > sql.ini file. Though it does not switch the connections automatically but if > the user tries to reconnect he gets routed through the new NIC interface. I > was hoping there is something similar to this in MS SQL server. I will try > my > luck in other forum. Thanks again. > > "Dan Guzman" wrote: > > >
Post Follow-up to this message Re: Multiple ListenersNIC teaming basically takes two or more NIC's and treats them as one NIC. There is only one IP. Teamed NIC's can be used for failure protection, as well a load balancing. You'd need to install the appropriate software to team the NIC's. For example, use BASP if you have Broadcom NIC's. http://www.broadcom.com/support/eth...faq_drivers.php Intel has an equivalent suite for their NIC's. I recently set up a cluster with teamed Broadcom NIC's. We pulled a cable out of one of the NIC's and the other just kept going. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Toronto, ON Canada "Jen" <Jen@discussions.microsoft.com> wrote in message news:B9F56B2C-E5B1-4622-B5E9- 8F9D03F2140E@microso ft.com... Thanks Tom, I am kinda new to databases. Your suggestion sounds interesting. Could you help me about how to setup "team the NIC's" stuff or point me to a place where I can grab more information? I did think of having multiple DNS entries but the third party application which we use, will need to be reconfigured everytime the primary NIC goes down. I am just hoping the user to restart the application and they get routed through a new NIC interface. Thank you both Tom and Dan. "Tom Moreau" wrote: > You may want to consider setting up DNS entries for each of the NIC's - or > you could team the NIC's. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > SQL Server MVP > Toronto, ON Canada > .. > "Jen" <Jen@discussions.microsoft.com> wrote in message > news:53A1EF0B-FAFA-4A6F-AB48- 54AC9484998E@microso ft.com... > Thanks Dan, you have been a great help. > > We are also running sybase, the multiple NIC client setup on sybase is > simple - just add multiple query entries with multiple IP address in the > sql.ini file. Though it does not switch the connections automatically but > if > the user tries to reconnect he gets routed through the new NIC interface. > I > was hoping there is something similar to this in MS SQL server. I will try > my > luck in other forum. Thanks again. > > "Dan Guzman" wrote: > > >
Post Follow-up to this message
Sponsored Links
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread
