named pipes
Tech-Archive recommends: Fix windows errors by optimizing your registry
The cluster consists of two nodes and of two instances. One default sql
instance and one another named instanse.
To connect to the named instance all the clients have alias(done by
cliconfg.exe), but when the instance fails over to another node no one
can't connect to this named instance anymore. If i edit the alias to
use the default instance pipe name, this helps!
It seems named pipes don't fail over to another node.. Any suggestions?
Thanks in advance.
Andrew
.
Relevant Pages
- Re: named pipes
... Columnist, SQL Server Professional ... To connect to the named instance all the clients have alias(done by ... but when the instance fails over to another node no one ... use the default instance pipe name, ...
(microsoft.public.sqlserver.clustering) - named pipes and sql server 2000 cluster
... One default sql ... To connect to the named instance all the clients have alias(done by ... but when the instance fails over to another node no one ... use the default instance pipe name, ...
(microsoft.public.sqlserver.connect) - SQL Failover problem.
... I have multiple instances of sql 2000 running on my windows 2003 cluster. ... I have the default instance owned by server1 and a named instance owner by ... If I shutdown server 1 then my default instance fails over to ...
(microsoft.public.sqlserver.clustering) - Re: SQL Failover problem.
... You can happily run a default instance and a named instance ... does the SQL Server resource try to start up and then fail? ... default instance) and in the NT event log on server1. ... If I shutdown server 1 then my default instance fails over to ...
(microsoft.public.sqlserver.clustering) - sql browser and named instance connection issue
... Checking file permisisons on:\Program Files\Microsoft SQL ... Restart SQLBrowser and then your named instance. ... The suggestions in the blog post include setting the Port property in SSAS ...
(microsoft.public.sqlserver.olap) |
|
