Re: connect to named instance in a cluster
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Thu, 9 Aug 2007 14:33:30 -0400
The short answer is that the behavior you observed is perfectly normal. SQL will decide on a port when the service restarts unless it is a default instance or you have locked SQL to a specific port number.
You can use the SQL Server Configuration Tool to "lock" the instance to a specific port. This is done whenever a client needs a static port to connect to.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Claudia" <Claudia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:17766F0D-BF9B-4DA1-9D1A-126B57E422B4@xxxxxxxxxxxxxxxx
Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
I have a N+1 cluster and installed default sql instance and one named
instance. SQL Browser service is running on the node which owns the named
instance; UDP port 1434 is opened on the firewall.
I had problem connecting to the named instance. Then I found the port number
in the sql error log which the named instance listens on. Opening this port
in firewall solved the connection problem.
My questions:
1. What's the best/secure way to connect to the named instance in a cluster?
Why does it not work with UDP opened and SQL Browser running before the
specific port is opened?
2. Will the port number change when the sql instance restarts? If yes, how
to assign a static port number?
Thanks.
Claudia
.
- Prev by Date: Re: Adding Disks
- Next by Date: Re: Clustering SQL Servers in a Workgroup
- Previous by thread: Adding Disks
- Next by thread: Re: Clustering SQL Servers in a Workgroup
- Index(es):
Relevant Pages
|
Loading