 | |
SQL Server instance naming
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#71
 
| |||
| |||
|
Re: SQL Server instance naming -
07-22-2008
, 07:33 PM
|
So I can connect to the second instance by using only the related virtual server name without the name of this instance, isn't it? Thanks "Denny Cherry" wrote: No, you would be able to connect to the virtual server name of the second instance. Don't forget that when you install SQL in a cluster each instance get's it's own hostname to go along with it's own IP address. On Mon, 21 Jul 2008 14:38:07 -0700, Pasquale Pasquale (AT) discussions (DOT) microsoft.com> wrote: In according with your first trick, I have to use the specific IP addresses instead of the virtual server name (without or with the instance name) for the client connectivity, isn't it? Thanks "Denny Cherry" wrote: The second instance on the cluster has to have a different name. One trick you can use is to tell the names instance to listen on port 1433 and stop the SQL Broker. This "should" allow the users to connect without putting in a name. You'll need to make sure that both instances on listening only on there specific IP Addresses otherwise you'll get port conflicts if the instances end up on the same node at any point. Another trick you can use is to use the Client Network Utility (c:\windows\system32\cliconfg.exe) and setup an alias so that SQLN2 actually points to SQLn2\InstanceName. This will need to be done on each users PC who needs to connect to the SQL Server. It is recommended that you simply connect to the instance name. Denny On Mon, 21 Jul 2008 13:35:00 -0700, Pasquale Pasquale (AT) discussions (DOT) microsoft.com> wrote: In a two node cluster (active/active), I have installed two SQL Server 2005 instances in order to use both nodes. The virtual server name of the first SQL instance owned by the node A is like SQLN1 (default instance) and the second SQL instance owned by the node B is like SQLN2 with a named instance SQLN2. Now I have seen that it is not possible a default instance for the instance owned by node B with the virtual server name SQLN2, isn't it? My customer would like to access the first instance with the virtual server name SQLN1 and to access the second instance with the virtual server name SQLN2: is it possible? How? Many thanks |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.