Right now we have to know, why the response from the SQL Server are sometimes too slow. We monitored the activity of the server and the RAM and CPU are OK, but we found some lost of packages during the data transfer... So we think now that the cause could be the Network Card (10/100/1000) and all the requests incoming from all the applications interacting whit it. Do you think that there's the possibility to decrease the response time with another Network Card? (Teaming) How handle it the SQL 2000?
Thanks a lot for your information.
Is the network interface card saturated? Even though it is 10/100/1000 NIC is it set to auto negotiate and the port in your switch set to auto negotiate? If it is flapping between 10, 100, or 1000 then you have a problem. Depending on the firmware of your switch and the driver of the NIC, you might be better setting the port and the NIC speed to 1000 FULL rather than AUTO. This was more common many years ago but could be your issue. As for teaming the NIC's, if you are not maxing out the Gigabit speed, then adding an additional NIC probably won't help a great deal.
Have you noticed that the performance issue is a specific time of day or very random? Is it for all connections or just a certain connection from a particular application server? The issue could be with the application or client and not with your database server.
Any addition information you can provide will help us help you.
answered Apr 28, 2012 at 05:36 PM
Have you spoken to the Network Team to find out exactly where packet loss is occuring?
The answer Tim provided is also valid. I had the same Problem where autonegotiation switched a 1000GBps Card to 10...
answered Dec 11, 2016 at 04:44 PM