November 12, 2008 at 7:46 am
We have a vendor application and few months back we rolled it out on our new SQL 2005 to find that apps were timing out, yes we tested thoroughly but on the go live this was happened.
Anyway what we found out was the Code was not working with TCP/IP but only with Named Pipes.
Our Application asks for the servername when loggin in.
Our servername is SERVERNAME.DOMAIN.LOCAL (When we use this the transactions come in using
TCP/IP).
When we use just SERVERNAME (Transactions comes in as Named Pipes).
The vendor has now released the software with the corrections for TCP/IP. Asking us to turn off named pipes - but this is not a dedicated server just for their app so we don't want to just turn off named pipes.
Because our users are used to just putting in just SERVERNAME only i need some way to make sure the transactions for this app use TCP/IP when the use SERVERNAME
Is there something i can set up in DNS or Alias that will default this to the TCP/IP ..I am guessing this would be the same as turning of named pipes ?
November 12, 2008 at 7:53 am
You could create an alias on the client end that specified TCP/IP.
November 12, 2008 at 8:06 am
You could create an alias on the client end that specified TCP/IP.
(in the CLICONFG I would add a Alias and add the Server Alias to be SERVERNAME and the
Connection Paramters to be SERVERNAME.DOMAIN.LOCAL
Is that what you mean.............
So every connection coming into the SQL would be TCP/IP.
Is it possible not to even use the servername but use one say FINANCEAPP instead and not even use the name of actual sql server as the names of our sql server are not user friendly.
Cheers
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply