The names (local) or (.) will always use the shared memory interface, rather than TCP or Named Pipes, and neither can be used against a clustered instance which requires TCP or Named Pipes over TCP. You can't use the shared memory interface against a non-local instance, which in the case of a cluster, the instance may or may not be local.
You must use the clustered Virtual SQL Service name, unfortunately localhost and (local) do not work on a cluster.
Have you tried "localhost" without ( and ).
Certain programs use (local), which is a sql connection string keyword apparently. My goal is to not have to get into the vendor supplied application and change it, otherwise I would just change it to the virtual SQL name. – Sam Jan 9 '09 at 23:57 I know (local) only when you try to access an special instance.
The cluster works on his virtual ip. – Bernd Ott Jan 11 '09 at 18:28.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.