Bimal

Thanks a lot for all your support Joseph, now we will try that option.

Namaste,
Bimal

Joseph,

Since the application is a thirdy party one we can not look into the functions, but I have checked the SQL tables which all of them are having indexes. Is there any debugging tool which we can use it for identifying the SQL sts from PROIV?

Namaste,

Bimal

Thanks Joseph for reply.

We have McAfee antivirus on all of servers and Norton on client side and updated on the fly all time. We used Distinct Netowork monitoring tool to identify the traffic between these two servers and found that 90% of traffic is TCP - TDS stream on port 1433 which is SQL server traffic and the rest is PROIV client connections through port 23. We tested by stopping PROIV service and then NIC traffic becomes normal. So it is genuine traffic. Is there any tweaking required on PROIV level to reduce the SQL traffic?

I will check with our Network administrator regarding the 'chatty' NIC.

Namaste,

Bimal