SQL Server Performance

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server

Discussion in 'Performance Tuning for DBAs' started by dbrandt, Dec 12, 2004.

  1. dbrandt New Member

    Hi, we are getting the above message regularly on an application we are running. Some preliminary reading suggests that we are not closing our connections and the system comes to a halt waiting for open connections to close until a new one is accepted. Does this sound right and if so is there a way around this?

  2. satya Moderator

    You need to try to capture the Winsock error message. Try making a network capture on both the client and server.

    PROFILER is the best tool to monitor the activity between client and server.

    Satya SKJ
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page