SQL 2005 Performance problem/question

[cburns70]

We having some strange performance issues with one or our SQL 2005 servers. Let me explain:

We have two Windows 2003 servers with MS SQL 2005 standard edition loaded. (server1, server2)

We have some workstations with XP Pro and some with Vista Ultimate loaded.

Using an XP PRO client machine we can connect to either server with NO performance issues.

If I use a VISTA machine, I can connect to server2 with NO performance issues, but if I try to connect to server1 the performance is extremly slow.

Its slow trying to setup an ODBC connection or even connecting with the SQL Management Studio. I've even tried using the SQL Native Client, but it gives me a time out error on Server1.

Since both servers work on XP, and only server1 as a problem with VISTA, we've concluded that the problem is on server1.

We checked every setting that we think of, and I tried some suggestions from the 'net but so far no luck.

I would appreciate any suggestions that anybody has to offer. Thanks.

 

[ptheriault]

I don't see how you have come to the conclusion the problem is with the database server???

It could be any number of issues. Are all the workstations on the same switch? Have you checked network packets.

also, If you want some help here you are going to have to provide us with as much details about the problem as you can.
I would start with some perfmon logs that can backup your conclusion.

There are so many things it could be we wouldn't know where to begin.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[aalmeida]

I ahve to agree with Paul I can see no basis to assume that the problem is with the Database Server, from what I understand, based on the provided explanations of the problem, the issue most likly lies on the network settings of that govern the connection between the 2.
More details are necessary but you can start asking questions like this: is it using TCPIP or Pipes?, is there a server alias on the local worstation?, is there conflicting IP addresses on local host file? etc...

AL Almeida
Senior DBA

http://www.ajmedia.net/

"May all those that come behind us, find us faithfull"

 

[cburns70]

Thanks for your replies. Here's alittle more info.

We have approximately 40 XP PRO client PCs that connect without any problem to Server 1. They are somewhat spread out at our facility, so they could be connecting through several different switches.

If I replace any of those PCs with a VISTA machine we immediately start having problems. Ping times are under 1ms, with no packet loss, from any PC to the Database server, even from a VISTA machine. We're using TCP/IP and there are no IP conflicts.

Since we have another SQL 2005 DB (server2) that is on the same network, and physically sits right next to server1, and doesn't experience the same problem when a VISTA machine connects to it, our assumption is there is some setting on server1 that has an effect when a VISTA machine connects to it.

Thanks again for your help.

 

[gmmastros]

I would suggest that you may have a DNS/WINS problem with the vista machines. I honestly don't know that much about DNS or WINS, but I know how to test this problem.

When connecting with SQL Server Management Studio... Instead of using the computer name of the server, type in the IP Address (where it prompts you for server).

You could also try modifying your ODBC connection to the use the IP Address instead of the server name.

If changing to IP addresses resolves your problem, then you (most likely) have a DNS/WINS problem.

Good luck.

-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[cburns70]

Thanks George, We had consider that possibilty as well. Unforunatly trying to connect use the IP address doesn't resolve the problem.

 

[aalmeida]

There is still one question left is the vista computer configured to use TCP/IP or Named Pipes?

AL Almeida
Senior DBA

http://www.ajmedia.net/

"May all those that come behind us, find us faithfull"

 

[cburns70]

We've tried both NP and TCP/IP with the same results.

I also checked for server alias as well. There was one alias for named pipes, the alias name was the same as the server name.

 

[aalmeida]

hmm ok then that could be it, NP is a slower connection type than TCP/IP and the server alias will override the ODBC connection.

If the 2005 SQL Server is accepting TCP/IP connections change the alias to use TCP/IP connection and use the port number instead of leting it discover the default.

Once you've done this let me know how it turns out.


AL Almeida
Senior DBA

http://www.ajmedia.net/

"May all those that come behind us, find us faithfull"

 

[cburns70]

I changed the alias to this:
Server alias = server1
Network Libray = TCP/IP
Connection properties = server1,1433

Still having same problem though.

 

[cburns70]

I found a work around for the problem. If I run this command from the VISTA machine:

netsh interface tcp set global autotuninglevel=disabled

the problem goes away.

I still curious why I only had this problem on one server. The servers appear to be setup the same, both have he same version of win2003 server.