August 18, 2005 at 1:37 am
We have a performance problem using a TCP/IP connection to connect to our SQL server.We switch to the named pipes protocol. The result was a much better performance. This only occurs when we connect from another server (Windows 2003 server). The application using the SQL server is running on Citrix servers.
I also tried to start the application from an other (not Citrix server), but the result (bad performance) is the same.
When we try to start the application from a workstation with Windows XP using the TCP/IP protocol, then the performance is OK.
So the problem is that when we connect to our SQL server from another server using a TCP/IP connection the performance is very bad. When we switch to Named Pipes the performance is much better.
TCP/IP should perform at least the same as Named Pipes, so there is something wrong. Does somebody know a solution, so we can switch back to the TCP/IP protocol.
August 19, 2005 at 7:08 am
Hello Leon,
does all your servers an workstations having the same SQL Server version?
In the past we encounter similar problems but it was not involving server to server connection just client to server. We were not able to point on the exact problem but since we were using different combination of SQL Server (2000 and 7), it seemed to be tightly related.
We also get the reverse problem (few months later): With TCP/IP the performance were good and with Named pipes they were bad.
Now we are in an SQL Server 2000 environnment (client and server) and everything seems to be fine with TCP/IP and with Named pipes.
Regards,
Carl
August 19, 2005 at 7:50 am
We have only one SQL server. This is a SQL Server 2000 SP3a. In our case, the client is a Citrix server. Our business application is running on the Citrix servers. This application connects to the SQL server. So we only have one version. It's a very strange problem.
August 19, 2005 at 8:13 am
Ok I suppose the client version of SQL Server on you Citrix Server is 2000 also. True?
With the same service pack?
Regards,
Carl
August 19, 2005 at 8:45 am
We don't have a SQL client installed on the Citrix servers. The only thing we did is that we made a System DSN for the Named Pipes configuration. The Citrix servers are Windows 2003.
Why do you need to install a SQL client ?? When we start the application from a workstation running Windows XP than we don't have a performance problem with the TCP/IP protocol. We didn't install a SQL client on the Windows XP clients.
August 19, 2005 at 9:31 am
Ok. You're rigth its not a must to install the client part of SQL Server.
Do you have the same MDAC version on your XP's workstation than the one on you 2003 Citrix Servers?
August 19, 2005 at 10:47 am
I would make sure that you are on MDAC v2.8 on the Citrix and on the SQL Server.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
August 19, 2005 at 12:28 pm
On both server (SQL and Citrix server) MDAC 2.8 is installed. So that shouldn't be the problem.
August 19, 2005 at 12:33 pm
Hello Leon,
I remember that in our case, to problem was related to MDAC.
So in your case, clearly, it seems to be something else.
If I think about something I'll let you know.
Regards,
Carl
August 22, 2005 at 9:40 pm
Have you thought about Name Resolution ? If you can put an entry into your Hosts file withthe server name and IP (and use that) then you won't have to rely on resolving the Server IP across the network. (If you can refer the connection to the Server Name.)
Or can you connect just using the IP address ?
..just guessing...
DB
The systems fine with no users loggged in. Can we keep it that way ?br>
August 23, 2005 at 9:00 am
Local hosts file entries and using IP addresses defeats the purpose of 'Name resolution' (not to mention that they can make for maintenance nightmares or better yet, hidden 'time bombs') ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
August 25, 2005 at 8:36 am
I checked the MDAC versions on all server. MDAC 2.8 RTM. All server are Windows 2003.
There is no problem with the dns server. Connecting using ip-adres in stead of the name makes no difference.
I don't want anything in de hosts files on the servers or workstations.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply