Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Using (local) in the connection string doesn’t work on my cluster. I’m assuming it’s looking for the default instance on the currently active node instead of the Virtual SQL name. Anyone know how to make this work?
edit note: I’d like to use (local) and not localhost – I don’t want to change any application generated code.
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.