Disconnect vs close window in SQL 2000

  • When I have finished a session in SQL 2K Query Analyzer I (religiously? superstitiously?) disconnect from the server and then close the window. I think that by doing this, I release the connection from the server memory pool. The developer across the aisle closes his Query Analyzer window using the close box when he has finished his queries. Does the procedure he uses needlessly waste server resources or am I just wasting mouse clicks by disconnecting every time?

    BTW, the server will not disconnect an idle connection. I don't make a practice of this, but if I leave a Query Analyzer window open and go to a meeting, the connection will still be alive when I get back.

  • Just looking strictly as the sysprocesses information, they do the exact same thing. I have one window open in SSMS to view the process data and then I open a QA connection once for clicking disconnect once for just closing the window. When I click disconnect the process goes away, when I just close the window the process goes away.

    I may be totally wrong and would not suggest you change the way you do things, but you probably are doing some extra clicks that are not necessary.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply